How severe is CVE-2014-9509?

No CVSS score has been assigned to CVE-2014-9509 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2014-9509?

CVE-2014-9509 affects the following packages: typo3/cms (Packagist), typo3/cms (Packagist), typo3/cms (Packagist), typo3/cms (Packagist), typo3/cms (Packagist), typo3/cms (Packagist), typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2014-9509?

Update typo3/cms to 4.5.39 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-9509 is resolved across your whole dependency graph.

How do I detect CVE-2014-9509 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2014-9509 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2014-9509?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2014-9509 can be triaged on real exposure rather than presence alone.

Is CVE-2014-9509 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2014-9509, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2014-9509?

CVE-2014-9509 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 73th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-9509?

CVE-2014-9509 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2014-9509 published, and has it been updated?

CVE-2014-9509 was published on May 17, 2022 and was last updated on November 29, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

CVE-2014-9509 — typo3/cms

CVE-2014-9509 is a Improper Input Validation vulnerability in typo3/cms. 1 public exploit reference exists, so weaponization risk is real. A fix is available for typo3/cms — see the affected versions and patch details below.

Typo3 Vulnerable to Cache Poisoning

Published

May 17, 2022

Updated

Nov 29, 2024

Affected

7 pkgs

Patched

7 / 7

Exploits

1 known

Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

7 pkgs affected

🐘typo3/cms🐘typo3/cms🐘typo3/cms🐘typo3/cms🐘typo3/cms🐘typo3/cms🐘typo3/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

Problem Description: A request URL with arbitrary arguments, but still pointing to the home page of a TYPO3 installation can be cached if the configuration option config.prefixLocalAnchors is used with the values "all" or "cached". The impact of this vulnerability is that unfamiliar looking links to the home page can end up in the cache, which leads to a reload of the page in the browser when section links are followed by web page visitors, instead of just directly jumping to the requested section of the page. TYPO3 versions 4.6.x and higher are only affected if the homepage is not a shortcut to a different page.

Solution: Removing the configuration options config.prefixLocalAnchors (and optionally also config.baseUrl) in favor of config.absRefPrefix

Credits: Thanks to Gernot Leitgab who discovered and reported the vulnerability.

Affected Packages

7 total 7 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms`	≥ 4.5.0&&< 4.5.39	4.5.39`composer require typo3/cms:^4.5.39`
🐘Packagist	`typo3/cms`	≥ 6.2.0&&< 6.2.9	6.2.9`composer require typo3/cms:^6.2.9`
🐘Packagist	`typo3/cms`	≥ 7.0.0&&< 7.0.2	7.0.2`composer require typo3/cms:^7.0.2`
🐘Packagist	`typo3/cms`	≥ 4.6.0&&< 4.6.19	4.6.19`composer require typo3/cms:^4.6.19`
🐘Packagist	`typo3/cms`	≥ 4.7.0&&< 4.7.21	4.7.21`composer require typo3/cms:^4.7.21`
🐘Packagist	`typo3/cms`	≥ 6.0.0&&< 6.0.15	6.0.15`composer require typo3/cms:^6.0.15`

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The frontend rendering component in TYPO3 4.5.x before 4.5.39, 4.6.x thr…

typo3.orgNVDJan 2015

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms to 4.5.39 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-9509 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2014-9509 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2014-9509. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

**Problem Description:** A request URL with arbitrary arguments, but still pointing to the home page of a TYPO3 installation can be cached if the configuration option `config.prefixLocalAnchors` is used with the values "all" or "cached". The impact of this vulnerability is that unfamiliar looking links to the home page can end up in the cache, which leads to a reload of the page in the browser when section links are followed by web page visitors, instead of just directly jumping to the requested section of the page. TYPO3 versions 4.6.x and higher are only affected if the homepage is not a sh

O3 Security · Impact-Aware SCA

Is CVE-2014-9509 in your dependencies?

O3 Security finds CVE-2014-9509 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works