How severe is GHSA-cvpc-hccg-wmw4?

GHSA-cvpc-hccg-wmw4 has a CVSS score of 6.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-cvpc-hccg-wmw4?

GHSA-cvpc-hccg-wmw4 affects the following packages: verbb/formie (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-cvpc-hccg-wmw4?

Update verbb/formie to 3.1.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cvpc-hccg-wmw4 is resolved across your whole dependency graph.

How do I detect GHSA-cvpc-hccg-wmw4 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for verbb/formie, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-cvpc-hccg-wmw4 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-cvpc-hccg-wmw4?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-cvpc-hccg-wmw4 can be triaged on real exposure rather than presence alone.

Is GHSA-cvpc-hccg-wmw4 actively exploited in the wild?

No public exploit code has been indexed for GHSA-cvpc-hccg-wmw4 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-cvpc-hccg-wmw4 published, and has it been updated?

GHSA-cvpc-hccg-wmw4 was published on July 17, 2026 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

GHSA-cvpc-hccg-wmw4 — verbb/formie

MEDIUM

GHSA-cvpc-hccg-wmw4 is a medium-severity (CVSS 6.3) vulnerability in verbb/formie. A fix is available for verbb/formie — see the affected versions and patch details below.

Formie: Missing authorization in administrative settings allows low-privileged CP users to modify plugin configuration

Published

Jul 17, 2026

Updated

Sep 10, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 10, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐘verbb/formie

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`verbb/formie`	all versions	3.1.28`composer require verbb/formie:^3.1.28`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for verbb/formie, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update verbb/formie to 3.1.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-cvpc-hccg-wmw4 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-cvpc-hccg-wmw4 can be triaged on real exposure rather than presence alone.

Tailored to GHSA-cvpc-hccg-wmw4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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-ex

O3 Security · Impact-Aware SCA

Is GHSA-cvpc-hccg-wmw4 in your dependencies?

O3 Security finds GHSA-cvpc-hccg-wmw4 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works