How severe is GHSA-jp3q-wwp3-pwv9?

No CVSS score has been assigned to GHSA-jp3q-wwp3-pwv9 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jp3q-wwp3-pwv9?

GHSA-jp3q-wwp3-pwv9 affects the following packages: solspace/craft-freeform (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-jp3q-wwp3-pwv9?

Update solspace/craft-freeform to 5.14.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jp3q-wwp3-pwv9 is resolved across your whole dependency graph.

How do I detect GHSA-jp3q-wwp3-pwv9 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-jp3q-wwp3-pwv9 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-jp3q-wwp3-pwv9?

O3 pinpoints whether GHSA-jp3q-wwp3-pwv9 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-jp3q-wwp3-pwv9 actively exploited in the wild?

No public exploit code has been indexed for GHSA-jp3q-wwp3-pwv9 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-jp3q-wwp3-pwv9?

GHSA-jp3q-wwp3-pwv9 has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 16th 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-jp3q-wwp3-pwv9 published, and has it been updated?

GHSA-jp3q-wwp3-pwv9 was published on January 22, 2026 and was last updated on February 13, 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-jp3q-wwp3-pwv9

Freeform Craft Plugin CP UI (builder/integrations) has Stored Cross-Site Scripting (XSS) issue

Also known asCVE-2026-26188

Published

Jan 22, 2026

Updated

Feb 13, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk16th percentile+0.21%

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

🐘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 An authenticated, low-privilege user (able to create/edit forms) can inject arbitrary HTML/JS into the Craft Control Panel (CP) builder and integrations views. User-controlled form labels and integration metadata are rendered with dangerouslySetInnerHTML without sanitization, leading to stored XSS that executes when any admin views the builder/integration screens.

Affected Product

Ecosystem: Packagist (Craft CMS plugin)
Package: solspace/craft-freeform
Version: <= 5.14.6 (latest observed). Likely all 5.x until patched.

Details

Root cause: Multiple user-controlled strings (field labels, section labels, integration icons, short names, WYSIWYG previews) are injected into React components using dangerouslySetInnerHTML without sanitization.
Evidence: dangerouslySetInnerHTML on user-controlled properties in bundled CP JS at packages/plugin/src/Resources/js/client/client.js.

PoCs

Label-based XSS:
1. In Craft CP, create/edit a Freeform field and set its label to <img src=x onerror="alert('xss-label')">.
2. Open the form builder view containing the field.
3. Alert executes (stored XSS).
Integration icon SVG:
1. Set an integration "icon SVG" to <svg><script>alert('xss-icon')</script></svg>.
2. Open the integrations CP view.
3. Script executes.

Impact Arbitrary JS in admin CP; session/CSRF token theft; potential full admin takeover via DOM-driven actions.

Remediation

Sanitize/HTML-encode all user-controlled strings before passing to dangerouslySetInnerHTML, or avoid it for labels/titles/icons.
Server-side: strip/escape disallowed tags on save for fields, integration metadata, WYSIWYG content.
Add regression tests with <img onerror> payloads to ensure no execution in builder/integration views.

Workarounds

Restrict form-edit permissions to trusted admins only until patched.
Consider CSP that disallows inline scripts (defense-in-depth only).

Credits

Discovered by https://www.linkedin.com/in/praveenkavinda/ | Prav33N-Sec.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`solspace/craft-freeform`	≥ 5.0.0&&< 5.14.7	5.14.7

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 5.14.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jp3q-wwp3-pwv9 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-jp3q-wwp3-pwv9 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-jp3q-wwp3-pwv9. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

**Summary** An authenticated, low-privilege user (able to create/edit forms) can inject arbitrary HTML/JS into the Craft Control Panel (CP) builder and integrations views. User-controlled form labels and integration metadata are rendered with `dangerouslySetInnerHTML` without sanitization, leading to stored XSS that executes when any admin views the builder/integration screens. **Affected Product** - Ecosystem: Packagist (Craft CMS plugin) - Package: solspace/craft-freeform - Version: <= 5.14.6 (latest observed). Likely all 5.x until patched. **Details** - Root cause: Multiple user-controlle

O3 Security · Impact-Aware SCA

Is GHSA-jp3q-wwp3-pwv9 in your dependencies?

O3 detects GHSA-jp3q-wwp3-pwv9 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