GHSA-cvpc-hccg-wmw4 json
Formie: Missing authorization in administrative settings allows low-privileged CP users to modify plugin configuration
published 3mo ago modified last mo.
- cvss
- 6.3
- version 3.1, GitHub
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no score, EPSS covers CVEs only
- public exploits
- 0
- none known
Summary
Formie contains a missing authorization vulnerability in administrative settings routes. An authenticated, non-admin Craft CMS control panel user with limited Formie access could directly access Formie settings pages and modify global plugin configuration.
In affected versions, Formie settings-related control panel routes did not consistently enforce the required settings permission on the server side. A low-privileged Craft CMS control panel user with limited Formie access could access /admin/formie/settings, save changes to global plugin settings, and access /admin/formie/settings/import-export.
The issue has been fixed by enforcing the formie-accessSettings permission across Formie settings controllers and related settings actions.
### Impact An authenticated low-privileged CP user may be able to: - Access Formie administrative settings. - Modify global Formie plugin configuration. - Access Formie import/export settings functionality.
This may allow configuration tampering and disruption of form-related workflows. Exploitation requires an authenticated Craft CMS control panel account.
Patch / fix
Is GHSA-cvpc-hccg-wmw4 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 6.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | verbb/formie | <3.1.28 |
3.1.28 |
Classification
- Weakness
-
- CWE-862 Missing Authorization
References
Sources
- GitHub Advisory GHSA-cvpc-hccg-wmw4
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.