How severe is GHSA-jfxf-4frr-9j3q?

No CVSS score has been assigned to GHSA-jfxf-4frr-9j3q yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-jfxf-4frr-9j3q?

GHSA-jfxf-4frr-9j3q affects the following packages: neos/neos (Packagist), neos/neos (Packagist), neos/neos (Packagist), neos/neos (Packagist), neos/neos (Packagist), neos/neos (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-jfxf-4frr-9j3q?

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.

How do I detect GHSA-jfxf-4frr-9j3q in my Packagist dependencies?

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

How do I mitigate GHSA-jfxf-4frr-9j3q if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Is GHSA-jfxf-4frr-9j3q actively exploited in the wild?

No public exploit code has been indexed for GHSA-jfxf-4frr-9j3q 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-jfxf-4frr-9j3q published, and has it been updated?

GHSA-jfxf-4frr-9j3q was published on May 25, 2022 and was last updated on December 7, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

XSS in various backend modules due to (un)escaping in…

Real-World Exposure

6 pkgs affected

🐘neos/neos🐘neos/neos🐘neos/neos🐘neos/neos🐘neos/neos🐘neos/neos

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

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

6 total 6 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`neos/neos`	≥ 3.3&&< 5.3.10	5.3.10`composer require neos/neos:^5.3.10`
🐘Packagist	`neos/neos`	≥ 7.0.0&&< 7.0.9	7.0.9`composer require neos/neos:^7.0.9`
🐘Packagist	`neos/neos`	≥ 7.1.0&&< 7.1.7	7.1.7`composer require neos/neos:^7.1.7`
🐘Packagist	`neos/neos`	≥ 7.2.0&&< 7.2.6	7.2.6`composer require neos/neos:^7.2.6`
🐘Packagist	`neos/neos`	≥ 7.3.0&&< 7.3.4	7.3.4`composer require neos/neos:^7.3.4`
🐘Packagist	`neos/neos`	≥ 8.0.0&&< 8.0.2	8.0.2`composer require neos/neos:^8.0.2`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for neos/neos, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-jfxf-4frr-9j3q in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

XSS in various backend modules due to (un)escaping in JS notification moduleGHSA-jfxf-4frr-9j3q