What is GHSA-JFXF-4FRR-9J3Q?

GHSA-JFXF-4FRR-9J3Q is a medium-severity cross-site scripting (XSS) vulnerability in neos/neos (composer), affecting versions >= 3.3, < 5.3.10. It is fixed in 5.3.10, 7.0.9, 7.1.7, 7.2.6, 7.3.4, 8.0.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

Which versions of neos/neos are affected by GHSA-JFXF-4FRR-9J3Q?

neos/neos (composer) versions >= 3.3, < 5.3.10 is affected.

Is there a fix for GHSA-JFXF-4FRR-9J3Q?

Yes. GHSA-JFXF-4FRR-9J3Q is fixed in 5.3.10, 7.0.9, 7.1.7, 7.2.6, 7.3.4, 8.0.2. Upgrade to this version or later.

Is GHSA-JFXF-4FRR-9J3Q exploitable, and should I be worried?

Whether GHSA-JFXF-4FRR-9J3Q is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-JFXF-4FRR-9J3Q is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

GHSA-JFXF-4FRR-9J3Q in neos/neos

Q: Which versions of neos/neos are affected by GHSA-JFXF-4FRR-9J3Q?

neos/neos (composer) versions >= 3.3, < 5.3.10 is affected.

Q: Is there a fix for GHSA-JFXF-4FRR-9J3Q?

Yes. GHSA-JFXF-4FRR-9J3Q is fixed in 5.3.10, 7.0.9, 7.1.7, 7.2.6, 7.3.4, 8.0.2. Upgrade to this version or later.

Q: Is GHSA-JFXF-4FRR-9J3Q exploitable, and should I be worried?

Whether GHSA-JFXF-4FRR-9J3Q is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-JFXF-4FRR-9J3Q is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-JFXF-4FRR-9J3Q?

Upgrade: neos/neos to 5.3.10 or later, neos/neos to 7.0.9 or later, neos/neos to 7.1.7 or later, neos/neos to 7.2.6 or later, neos/neos to 7.3.4 or later, neos/neos to 8.0.2 or later.

Summary

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

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.

Impact

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Affected versions

neos/neos (>= 3.3, < 5.3.10) neos/neos (>= 7.0.0, < 7.0.9) neos/neos (>= 7.1.0, < 7.1.7) neos/neos (>= 7.2.0, < 7.2.6) neos/neos (>= 7.3.0, < 7.3.4) neos/neos (>= 8.0.0, < 8.0.2)

Security releases

neos/neos → 5.3.10 (composer) neos/neos → 7.0.9 (composer) neos/neos → 7.1.7 (composer) neos/neos → 7.2.6 (composer) neos/neos → 7.3.4 (composer) neos/neos → 8.0.2 (composer)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade the following packages to resolve this vulnerability:

neos/neos to 5.3.10 or later; neos/neos to 7.0.9 or later; neos/neos to 7.1.7 or later; neos/neos to 7.2.6 or later; neos/neos to 7.3.4 or later; neos/neos to 8.0.2 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is GHSA-JFXF-4FRR-9J3Q? GHSA-JFXF-4FRR-9J3Q is a medium-severity cross-site scripting (XSS) vulnerability in neos/neos (composer), affecting versions >= 3.3, < 5.3.10. It is fixed in 5.3.10, 7.0.9, 7.1.7, 7.2.6, 7.3.4, 8.0.2. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
Which versions of neos/neos are affected by GHSA-JFXF-4FRR-9J3Q? neos/neos (composer) versions >= 3.3, < 5.3.10 is affected.
Is there a fix for GHSA-JFXF-4FRR-9J3Q? Yes. GHSA-JFXF-4FRR-9J3Q is fixed in 5.3.10, 7.0.9, 7.1.7, 7.2.6, 7.3.4, 8.0.2. Upgrade to this version or later.
Is GHSA-JFXF-4FRR-9J3Q exploitable, and should I be worried? Whether GHSA-JFXF-4FRR-9J3Q is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-JFXF-4FRR-9J3Q is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-JFXF-4FRR-9J3Q?
- Upgrade neos/neos to 5.3.10 or later
- Upgrade neos/neos to 7.0.9 or later
- Upgrade neos/neos to 7.1.7 or later
- Upgrade neos/neos to 7.2.6 or later
- Upgrade neos/neos to 7.3.4 or later
- Upgrade neos/neos to 8.0.2 or later

Other vulnerabilities in neos/neos

CVE-IDSeverityPackage summary

GHSA-6CJ3-RC4P-F38FHighneos/neos: Cross-site Scripting vulnerabilities in Neos GHSA-43CF-7F3H-38RGMediumneos/neos: Privilege Escalation in TYPO3 Neos GHSA-3C5G-73F7-GRVMHighneos/neos: Neos Information Disclosure Security Note CVE-2022-30429Mediumneos/neos: Neos CMS vulnerable to XSS in various backend modules