GHSA-jfxf-4frr-9j3q
XSS in various backend modules due to (un)escaping in JS notification module
Blast Radius
neos/neos🐘neos/neos🐘neos/neos🐘neos/neos🐘neos/neos🐘neos/neosReal-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
The notification module displaying flash messages unscapes HTML coming from the server, resulting in XSS vulnerabilities with various names and labels of entities (eg. workspace title or media title). This however means you must be a logged in user with respective rights in the first place to leverage the attack vector.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | neos/neos | ≥ 3.3&&< 5.3.10 | 5.3.10 |
| 🐘Packagist | neos/neos | ≥ 7.0.0&&< 7.0.9 | 7.0.9 |
| 🐘Packagist | neos/neos | ≥ 7.1.0&&< 7.1.7 | 7.1.7 |
| 🐘Packagist | neos/neos | ≥ 7.2.0&&< 7.2.6 | 7.2.6 |
| 🐘Packagist | neos/neos | ≥ 7.3.0&&< 7.3.4 | 7.3.4 |
| 🐘Packagist | neos/neos | ≥ 8.0.0&&< 8.0.2 | 8.0.2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neos/neos. 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 neos/neos to 5.3.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jfxf-4frr-9j3q 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-jfxf-4frr-9j3q 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-jfxf-4frr-9j3q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-jfxf-4frr-9j3q in your dependencies?
O3 detects GHSA-jfxf-4frr-9j3q across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.