How severe is GHSA-p84g-j2gh-83g3?

No CVSS score has been assigned to GHSA-p84g-j2gh-83g3 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-p84g-j2gh-83g3?

GHSA-p84g-j2gh-83g3 affects the following packages: typo3/cms (Packagist), typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-p84g-j2gh-83g3?

Update typo3/cms to 6.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p84g-j2gh-83g3 is resolved across your whole dependency graph.

How do I detect GHSA-p84g-j2gh-83g3 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 GHSA-p84g-j2gh-83g3 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.

Is GHSA-p84g-j2gh-83g3 actively exploited in the wild?

No public exploit code has been indexed for GHSA-p84g-j2gh-83g3 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-p84g-j2gh-83g3 published, and has it been updated?

GHSA-p84g-j2gh-83g3 was published on May 30, 2024 and was last updated on December 6, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

TYPO3 possible cache poisoning on the homepage when…

Real-World Exposure

2 pkgs affected

🐘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

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.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘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`

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 6.2.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p84g-j2gh-83g3 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.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is GHSA-p84g-j2gh-83g3 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

TYPO3 possible cache poisoning on the homepage when anchors are usedGHSA-p84g-j2gh-83g3