Summary
Typo3 Open Redirect In Frontend Rendering
The frontend rendering component in TYPO3 4.5.x before 4.5.39, 4.6.x through 6.2.x before 6.2.9, and 7.x before 7.0.2, allows remote attackers to change URLs to arbitrary domains.
An attacker could forge a request which modifies anchor only links on the homepage of a TYPO3 installation such that they point to arbitrary domains, if the configuration option config.prefixLocalAnchors is used with any possible value. TYPO3 versions 4.6.x and higher are only affected if the homepage is not a shortcut to a different page. As an additional pre-condition, URL rewriting must be enabled in the web server (which it typically is) when using extensions like realurl or cooluri.
Installations where config.absRefPrefix is additionally set to any value are not affected by this vulnerability.
Example of affected configuration:
config.absRefPrefix =
config.prefixLocalAnchors = all
page = PAGE
page.10 = TEXT
page.10.value = <a href="#skiplinks">Skiplinks</a>
.htaccess:
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteCond %{REQUEST_FILENAME} !-l
RewriteRule .* index.php [L]
Impact
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 4.5.39 or later; typo3/cms to 6.2.9 or later; typo3/cms to 7.0.2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2014-9508? CVE-2014-9508 is a medium-severity security vulnerability in typo3/cms (composer), affecting versions >= 4.5.0, < 4.5.39. It is fixed in 4.5.39, 6.2.9, 7.0.2.
- Which versions of typo3/cms are affected by CVE-2014-9508? typo3/cms (composer) versions >= 4.5.0, < 4.5.39 is affected.
- Is there a fix for CVE-2014-9508? Yes. CVE-2014-9508 is fixed in 4.5.39, 6.2.9, 7.0.2. Upgrade to this version or later.
- Is CVE-2014-9508 exploitable, and should I be worried? Whether CVE-2014-9508 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 CVE-2014-9508 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 CVE-2014-9508?
- Upgrade
typo3/cmsto 4.5.39 or later - Upgrade
typo3/cmsto 6.2.9 or later - Upgrade
typo3/cmsto 7.0.2 or later
- Upgrade