How severe is GHSA-rwr8-xrpw-9qf5?

No CVSS score has been assigned to GHSA-rwr8-xrpw-9qf5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-rwr8-xrpw-9qf5?

GHSA-rwr8-xrpw-9qf5 affects the following packages: solspace/craft-freeform (Packagist), solspace/craft-freeform (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-rwr8-xrpw-9qf5?

Update solspace/craft-freeform to 4.1.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rwr8-xrpw-9qf5 is resolved across your whole dependency graph.

How do I detect GHSA-rwr8-xrpw-9qf5 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for solspace/craft-freeform. 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-rwr8-xrpw-9qf5 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-rwr8-xrpw-9qf5?

O3 pinpoints whether GHSA-rwr8-xrpw-9qf5 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-rwr8-xrpw-9qf5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-rwr8-xrpw-9qf5 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-rwr8-xrpw-9qf5 published, and has it been updated?

GHSA-rwr8-xrpw-9qf5 was published on January 15, 2026 and was last updated on February 3, 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

GHSA-rwr8-xrpw-9qf5

solspace/craft-freeform Exposed to Known Axios Vulnerabilities via Precompiled Assets

Published

Jan 15, 2026

Updated

Feb 3, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

🐘solspace/craft-freeform🐘solspace/craft-freeform

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

Summary

The latest versions of both 4.x and 5.x are using Axios versions < 1.7.5 and as such are subject to known vulnerabilities as per: https://security.snyk.io/package/npm/axios

Details

We've had this flagged up in a pen test, which indicates the issue stems from this script: /freeform/plugin.js. I couldn't see any reference to vulnerable axios versions in your package.json files, but noticed some precompiled files in packages/plugin so I'm assuming those are where the issue lies.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`solspace/craft-freeform`	all versions	4.1.22
🐘Packagist	`solspace/craft-freeform`	≥ 5.0.0-beta.1&&< 5.5.9	5.5.9

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for solspace/craft-freeform. 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 solspace/craft-freeform to 4.1.22 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rwr8-xrpw-9qf5 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-rwr8-xrpw-9qf5 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-rwr8-xrpw-9qf5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary The latest versions of both 4.x and 5.x are using Axios versions < 1.7.5 and as such are subject to known vulnerabilities as per: https://security.snyk.io/package/npm/axios ### Details We've had this flagged up in a pen test, which indicates the issue stems from this script: /freeform/plugin.js. I couldn't see any reference to vulnerable axios versions in your package.json files, but noticed some precompiled files in packages/plugin so I'm assuming those are where the issue lies.

O3 Security · Impact-Aware SCA

Is GHSA-rwr8-xrpw-9qf5 in your dependencies?

O3 detects GHSA-rwr8-xrpw-9qf5 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