Formie: Missing authorization in administrative settings allows low-privileged CP users to modify plugin configuration
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (verbb/formie 3.1.28), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist verbb/formie
- Affected
- < 3.1.28
- Fixed in
- 3.1.28
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-cvpc-hccg-wmw4 lists affected ranges: Packagist verbb/formie >=0 <3.1.28
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
- EPSS
- No dated EPSS signal available.
Source description
As published by the source; long descriptions are shortened.
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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-cvpc-hccg-wmw4
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: GHSA-cvpc-hccg-wmw4 Advisory: Formie: Missing authorization in administrative settings allows low-privileged CP users to modify plugin configuration IDs: GHSA-cvpc-hccg-wmw4 Record: https://patchnext.com/advisories/ghsa-cvpc-hccg-wmw4 (revision 1, source checked 26 Oct 2026, 14:50 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: verbb/formie 3.1.28. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist verbb/formie: affected < 3.1.28; fixed in 3.1.28 ## Suggested inspection (read-only) - Packagist verbb/formie: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on verbb/formie. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-cvpc-hccg-wmw4 (GitHub-reviewed advisory GHSA-cvpc-hccg-wmw4 lists affected ranges: Packagist verbb/formie >=0 <3.1.28) Commands are suggestions: review each one before running it.
Loading voting…