How severe is GHSA-p9hh-mh5x-wvx3?

No CVSS score has been assigned to GHSA-p9hh-mh5x-wvx3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p9hh-mh5x-wvx3?

GHSA-p9hh-mh5x-wvx3 affects the following packages: verbb/formie (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-p9hh-mh5x-wvx3?

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

How do I detect GHSA-p9hh-mh5x-wvx3 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for verbb/formie. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-p9hh-mh5x-wvx3 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-p9hh-mh5x-wvx3?

O3 pinpoints whether GHSA-p9hh-mh5x-wvx3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-p9hh-mh5x-wvx3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p9hh-mh5x-wvx3 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.

What is the EPSS score for GHSA-p9hh-mh5x-wvx3?

GHSA-p9hh-mh5x-wvx3 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 8th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

When was GHSA-p9hh-mh5x-wvx3 published, and has it been updated?

GHSA-p9hh-mh5x-wvx3 was published on April 11, 2025 and was last updated on April 11, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-p9hh-mh5x-wvx3

Formie has XSS vulnerability for importing forms

Also known asCVE-2025-32427

Published

Apr 11, 2025

Updated

Apr 11, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk8th percentile-0.17%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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

Impact

When importing a form from JSON, if the field label or handle contained malicious content, the output wasn't correctly escaped when viewing a preview of what was to be imported.

As imports are undertaking primarily by users who have themselves exported the form from one environment to another, and would require direct manipulation of the JSON export, this is marked as moderate. This vulnerability will not occur unless someone deliberately tampers with the export.

Patches

This has been fixed in Formie 2.1.44. Users should ensure they are running at least this version.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`verbb/formie`	all versions	2.1.44

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update verbb/formie to 2.1.44 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p9hh-mh5x-wvx3 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 pinpoints whether GHSA-p9hh-mh5x-wvx3 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

Frequently Asked Questions

### Impact When importing a form from JSON, if the field label or handle contained malicious content, the output wasn't correctly escaped when viewing a preview of what was to be imported. As imports are undertaking primarily by users who have themselves exported the form from one environment to another, and would require direct manipulation of the JSON export, this is marked as moderate. This vulnerability will not occur unless someone deliberately tampers with the export. ### Patches This has been fixed in Formie 2.1.44. Users should ensure they are running at least this version.

O3 Security · Impact-Aware SCA

Is GHSA-p9hh-mh5x-wvx3 in your dependencies?

O3 detects GHSA-p9hh-mh5x-wvx3 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works