Summary
Missing Access Check in TYPO3 CMS
Extbase request handling fails to implement a proper access check for requested controller/ action combinations, which makes it possible for an attacker to execute arbitrary Extbase actions by crafting a special request. To successfully exploit this vulnerability, an attacker must have access to at least one Extbase plugin or module action in a TYPO3 installation. The missing access check inevitably leads to information disclosure or remote code execution, depending on the action that an attacker is able to execute.
Impact
GHSA-GWFX-P7MR-F92V has a CVSS score of 9.0 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.2.25, 7.6.8, 8.1.1); upgrading removes the vulnerable code path.
Affected versions
Security releases
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 environmentNew to Kodem? Get a demo →Remediation advice
typo3/cms to 6.2.25 or later; typo3/cms to 7.6.8 or later; typo3/cms to 8.1.1 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-GWFX-P7MR-F92V? GHSA-GWFX-P7MR-F92V is a critical-severity security vulnerability in typo3/cms (composer), affecting versions >= 6.2.0, < 6.2.25. It is fixed in 6.2.25, 7.6.8, 8.1.1.
- How severe is GHSA-GWFX-P7MR-F92V? GHSA-GWFX-P7MR-F92V has a CVSS score of 9.0 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of typo3/cms are affected by GHSA-GWFX-P7MR-F92V? typo3/cms (composer) versions >= 6.2.0, < 6.2.25 is affected.
- Is there a fix for GHSA-GWFX-P7MR-F92V? Yes. GHSA-GWFX-P7MR-F92V is fixed in 6.2.25, 7.6.8, 8.1.1. Upgrade to this version or later.
- Is GHSA-GWFX-P7MR-F92V exploitable, and should I be worried? Whether GHSA-GWFX-P7MR-F92V 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-GWFX-P7MR-F92V 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-GWFX-P7MR-F92V?
- Upgrade
typo3/cmsto 6.2.25 or later - Upgrade
typo3/cmsto 7.6.8 or later - Upgrade
typo3/cmsto 8.1.1 or later
- Upgrade