How severe is GHSA-qffc-gwpp-m2xr?

No CVSS score has been assigned to GHSA-qffc-gwpp-m2xr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-qffc-gwpp-m2xr?

GHSA-qffc-gwpp-m2xr affects the following packages: typo3/cms (Packagist), typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-qffc-gwpp-m2xr?

Update typo3/cms to 6.2.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qffc-gwpp-m2xr is resolved across your whole dependency graph.

How do I detect GHSA-qffc-gwpp-m2xr 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-qffc-gwpp-m2xr if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-qffc-gwpp-m2xr actively exploited in the wild?

No public exploit code has been indexed for GHSA-qffc-gwpp-m2xr 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-qffc-gwpp-m2xr published, and has it been updated?

GHSA-qffc-gwpp-m2xr was published on June 4, 2024 and was last updated on December 1, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

XML External Entity (XXE) Processing in TYPO3 Core

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

All XML processing within the TYPO3 CMS are vulnerable to XEE processing. This can lead to load internal and/or external (file) content within an XML structure. Furthermore it is possible to inject arbitrary files for an XML Denial of Service attack. For more information on that topic see https://www.owasp.org/index.php/XML_External_Entity_(XXE)_Processing.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms`	≥ 6.2.0&&< 6.2.19	6.2.19`composer require typo3/cms:^6.2.19`
🐘Packagist	`typo3/cms`	≥ 7.6.0&&< 7.6.4	7.6.4`composer require typo3/cms:^7.6.4`

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.19 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qffc-gwpp-m2xr is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

All XML processing within the TYPO3 CMS are vulnerable to XEE processing. This can lead to load internal and/or external (file) content within an XML structure. Furthermore it is possible to inject arbitrary files for an XML Denial of Service attack. For more information on that topic see https://www.owasp.org/index.php/XML_External_Entity_(XXE)_Processing.

O3 Security · Impact-Aware SCA

Is GHSA-qffc-gwpp-m2xr in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

XML External Entity (XXE) Processing in TYPO3 CoreGHSA-qffc-gwpp-m2xr