Summary
Cache Flooding in TYPO3 Frontend
Links with a valid cHash argument lead to newly generated page cache entries. Because the cHash is not bound to a specific page, attackers could use valid cHash arguments for multiple pages, leading to additional useless page cache entries. Depending on the number of pages in the system and the number of available valid links with a cHash, attackers could add a considerable amount of additional cache entries, which in the end exceed storage limits and thus could lead to the system not responding any more. This means the Cache Flooding attack potentially could lead to a successful Denial of Service (DoS) attack.
Impact
GHSA-PW2Q-QWVJ-GH43 has a CVSS score of 5.3 (Medium). 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.27, 7.6.11, 8.3.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.27 or later; typo3/cms to 7.6.11 or later; typo3/cms to 8.3.1 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-PW2Q-QWVJ-GH43? GHSA-PW2Q-QWVJ-GH43 is a medium-severity security vulnerability in typo3/cms (composer), affecting versions >= 6.2.0, < 6.2.27. It is fixed in 6.2.27, 7.6.11, 8.3.1.
- How severe is GHSA-PW2Q-QWVJ-GH43? GHSA-PW2Q-QWVJ-GH43 has a CVSS score of 5.3 (Medium). 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-PW2Q-QWVJ-GH43? typo3/cms (composer) versions >= 6.2.0, < 6.2.27 is affected.
- Is there a fix for GHSA-PW2Q-QWVJ-GH43? Yes. GHSA-PW2Q-QWVJ-GH43 is fixed in 6.2.27, 7.6.11, 8.3.1. Upgrade to this version or later.
- Is GHSA-PW2Q-QWVJ-GH43 exploitable, and should I be worried? Whether GHSA-PW2Q-QWVJ-GH43 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-PW2Q-QWVJ-GH43 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-PW2Q-QWVJ-GH43?
- Upgrade
typo3/cmsto 6.2.27 or later - Upgrade
typo3/cmsto 7.6.11 or later - Upgrade
typo3/cmsto 8.3.1 or later
- Upgrade