What is GHSA-G4XV-R3QW-V3Q2?

GHSA-G4XV-R3QW-V3Q2 is a high-severity security vulnerability in typo3/neos (composer), affecting versions >= 2.3.0, < 2.3.99. It is fixed in 2.3.99, 3.0.20, 3.1.18, 3.2.14, 3.3.23, 4.0.17, 4.1.16, 4.2.12, 4.3.3.

Which versions of typo3/neos are affected by GHSA-G4XV-R3QW-V3Q2?

typo3/neos (composer) versions >= 2.3.0, < 2.3.99 is affected.

Is there a fix for GHSA-G4XV-R3QW-V3Q2?

Yes. GHSA-G4XV-R3QW-V3Q2 is fixed in 2.3.99, 3.0.20, 3.1.18, 3.2.14, 3.3.23, 4.0.17, 4.1.16, 4.2.12, 4.3.3. Upgrade to this version or later.

Is GHSA-G4XV-R3QW-V3Q2 exploitable, and should I be worried?

Whether GHSA-G4XV-R3QW-V3Q2 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-G4XV-R3QW-V3Q2 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-G4XV-R3QW-V3Q2 in typo3/neos

Q: Which versions of typo3/neos are affected by GHSA-G4XV-R3QW-V3Q2?

typo3/neos (composer) versions >= 2.3.0, < 2.3.99 is affected.

Q: Is there a fix for GHSA-G4XV-R3QW-V3Q2?

Yes. GHSA-G4XV-R3QW-V3Q2 is fixed in 2.3.99, 3.0.20, 3.1.18, 3.2.14, 3.3.23, 4.0.17, 4.1.16, 4.2.12, 4.3.3. Upgrade to this version or later.

Q: Is GHSA-G4XV-R3QW-V3Q2 exploitable, and should I be worried?

Whether GHSA-G4XV-R3QW-V3Q2 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-G4XV-R3QW-V3Q2 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-G4XV-R3QW-V3Q2?

Upgrade: typo3/neos to 2.3.99 or later, typo3/neos to 3.0.20 or later, typo3/neos to 3.1.18 or later, typo3/neos to 3.2.14 or later, typo3/neos to 3.3.23 or later, typo3/neos to 4.0.17 or later, typo3/neos to 4.1.16 or later, typo3/neos to 4.2.12 or later, typo3/neos to 4.3.3 or later.

Summary

typo3 Information Disclosure Security Note

Due to reports it has been validated that internal workspaces in Neos are accessible without authentication. Some users assumed this is a planned feature but it is not. A workspace preview should be an additional feature with respective security measures in place.

Note that this only allows reading of internal workspaces not writing. And for clarification, an internal workspace is a workspace that is non public and doesn't have an owner.

Given that an internal workspace exists in your installation, it is possible to view a page in context of that workspace by opening a link in this format:

https://domain/path/to/page.html@workspace-name

The issue is quite problematic when exploited but at the same time slightly less impactful than it sounds. First of all there is no default internal workspace, so the issue affects only workspaces created by users. That also means the workspace-name, which will also always include a hash is individual to a project and an exploiter must get hold of the workspace-name including the hash. This is non trivial as there is no indication of the existence of it, but obviously brute force and educated guessed can be made.

Impact

Affected versions

typo3/neos (>= 2.3.0, < 2.3.99) typo3/neos (>= 3.0.0, < 3.0.20) typo3/neos (>= 3.1.0, < 3.1.18) typo3/neos (>= 3.2.0, < 3.2.14) typo3/neos (>= 3.3.0, < 3.3.23) typo3/neos (>= 4.0.0, < 4.0.17) typo3/neos (>= 4.1.0, < 4.1.16) typo3/neos (>= 4.2.0, < 4.2.12) typo3/neos (>= 4.3.0, < 4.3.3)

Security releases

typo3/neos → 2.3.99 (composer) typo3/neos → 3.0.20 (composer) typo3/neos → 3.1.18 (composer) typo3/neos → 3.2.14 (composer) typo3/neos → 3.3.23 (composer) typo3/neos → 4.0.17 (composer) typo3/neos → 4.1.16 (composer) typo3/neos → 4.2.12 (composer) typo3/neos → 4.3.3 (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:

typo3/neos to 2.3.99 or later; typo3/neos to 3.0.20 or later; typo3/neos to 3.1.18 or later; typo3/neos to 3.2.14 or later; typo3/neos to 3.3.23 or later; typo3/neos to 4.0.17 or later; typo3/neos to 4.1.16 or later; typo3/neos to 4.2.12 or later; typo3/neos to 4.3.3 or later

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

Frequently Asked Questions

What is GHSA-G4XV-R3QW-V3Q2? GHSA-G4XV-R3QW-V3Q2 is a high-severity security vulnerability in typo3/neos (composer), affecting versions >= 2.3.0, < 2.3.99. It is fixed in 2.3.99, 3.0.20, 3.1.18, 3.2.14, 3.3.23, 4.0.17, 4.1.16, 4.2.12, 4.3.3.
Which versions of typo3/neos are affected by GHSA-G4XV-R3QW-V3Q2? typo3/neos (composer) versions >= 2.3.0, < 2.3.99 is affected.
Is there a fix for GHSA-G4XV-R3QW-V3Q2? Yes. GHSA-G4XV-R3QW-V3Q2 is fixed in 2.3.99, 3.0.20, 3.1.18, 3.2.14, 3.3.23, 4.0.17, 4.1.16, 4.2.12, 4.3.3. Upgrade to this version or later.
Is GHSA-G4XV-R3QW-V3Q2 exploitable, and should I be worried? Whether GHSA-G4XV-R3QW-V3Q2 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-G4XV-R3QW-V3Q2 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-G4XV-R3QW-V3Q2?
- Upgrade typo3/neos to 2.3.99 or later
- Upgrade typo3/neos to 3.0.20 or later
- Upgrade typo3/neos to 3.1.18 or later
- Upgrade typo3/neos to 3.2.14 or later
- Upgrade typo3/neos to 3.3.23 or later
- Upgrade typo3/neos to 4.0.17 or later
- Upgrade typo3/neos to 4.1.16 or later
- Upgrade typo3/neos to 4.2.12 or later
- Upgrade typo3/neos to 4.3.3 or later

Other vulnerabilities in typo3/neos

CVE-IDSeverityPackage summary

GHSA-WR3C-6C22-M9V6Mediumtypo3/neos: Privilege Escalation in TYPO3 Neos GHSA-4542-P56H-8XWWHightypo3/neos: Cross-Site Scripting (XSS) vulnerabilities in Neos