Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist
Not in CISA KEV

GHSA-jfxf-4frr-9j3q neos/neos

GHSA-jfxf-4frr-9j3q is a security vulnerability in neos/neos. A fix is available for neos/neos — see the affected versions and patch details below.

XSS in various backend modules due to (un)escaping in JS notification module

Published
May 25, 2022
Updated
Dec 7, 2024
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed
Exploitation data as of Dec 7, 2024 · OSV.dev, FIRST.org (EPSS)

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
EcosystemPackageVulnerable rangeFix
🐘Packagistneos/neos3.3&&< 5.3.105.3.10composer require neos/neos:^5.3.10
🐘Packagistneos/neos7.0.0&&< 7.0.97.0.9composer require neos/neos:^7.0.9
🐘Packagistneos/neos7.1.0&&< 7.1.77.1.7composer require neos/neos:^7.1.7
🐘Packagistneos/neos7.2.0&&< 7.2.67.2.6composer require neos/neos:^7.2.6
🐘Packagistneos/neos7.3.0&&< 7.3.47.3.4composer require neos/neos:^7.3.4
🐘Packagistneos/neos8.0.0&&< 8.0.28.0.2composer require neos/neos:^8.0.2

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. 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.

  3. 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.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-jfxf-4frr-9j3q can be triaged on real exposure rather than presence alone.

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

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?

O3 Security finds GHSA-jfxf-4frr-9j3q across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-jfxf-4frr-9j3q: neos/neos XSS | O3 Security