Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

Typo3 Vulnerable to Cache Poisoning

CVE-2014-9509GHSA-5479-gqqr-f9gj

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (typo3/cms 7.0.2, 6.2.9, 6.1.13, 6.0.15, 4.7.21, 4.6.19, 4.5.39), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist typo3/cms

    Affected
    >= 4.5.0, < 4.5.39>= 6.2.0, < 6.2.9>= 7.0.0, < 7.0.2>= 4.6.0, <= 4.6.18>= 4.7.0, <= 4.7.20>= 6.0.0, <= 6.0.14>= 6.1.0, <= 6.1.12
    Fixed in
    6.0.15, 6.2.9, 4.7.21, 4.5.39, 4.6.19, 7.0.2, 6.1.13

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2014-9509: 1.50% estimated exploitation activity in the next 30 days; percentile 74.23 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-5479-gqqr-f9gj

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2014-9509

Advisory: Typo3 Vulnerable to Cache Poisoning
IDs: CVE-2014-9509, GHSA-5479-gqqr-f9gj
Record: https://patchnext.com/advisories/cve-2014-9509 (revision 1, source checked 26 Oct 2026, 14:09 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms 7.0.2, 6.2.9, 6.1.13, 6.0.15, 4.7.21, 4.6.19, 4.5.39. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms: affected >= 4.5.0, < 4.5.39; >= 6.2.0, < 6.2.9; >= 7.0.0, < 7.0.2; >= 4.6.0, <= 4.6.18; >= 4.7.0, <= 4.7.20; >= 6.0.0, <= 6.0.14; >= 6.1.0, <= 6.1.12; fixed in 6.0.15, 6.2.9, 4.7.21, 4.5.39, 4.6.19, 7.0.2, 6.1.13

## Suggested inspection (read-only)
- Packagist typo3/cms: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typo3/cms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-5479-gqqr-f9gj (GitHub-reviewed advisory GHSA-5479-gqqr-f9gj lists affected ranges: Packagist typo3/cms >=4.5.0 =6.2.0 =7.0.0 =4.6.0 =4.7.0 =6.0.0 =6.1.0 <=6.1.12)

Commands are suggestions: review each one before running it.

Loading voting…