CVE-2024-25119 is a medium-severity (CVSS 4.9) Information Exposure vulnerability in typo3/cms-core. A fix is available for typo3/cms-core — see the affected versions and patch details below.
Information Disclosure of Encryption Key in TYPO3 Install Tool
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-25119.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-coreReal-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
TYPO3 is an open source PHP based web content management system released under the GNU GPL. The plaintext value of $GLOBALS['SYS']['encryptionKey'] was displayed in the editing forms of the TYPO3 Install Tool user interface. This allowed attackers to utilize the value to generate cryptographic hashes used for verifying the authenticity of HTTP request parameters. Exploiting this vulnerability requires an administrator-level backend user account with system maintainer permissions. Users are advised to update to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described. There are no known workarounds for this vulnerability.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-core | ≥ 8.0.0&&< 8.7.57 | 8.7.57composer require typo3/cms-core:^8.7.57 |
| 🐘Packagist | typo3/cms-core | ≥ 9.0.0&&< 9.5.46 | 9.5.46composer require typo3/cms-core:^9.5.46 |
| 🐘Packagist | typo3/cms-core | ≥ 10.0.0&&< 10.4.43 | 10.4.43composer require typo3/cms-core:^10.4.43 |
| 🐘Packagist | typo3/cms-core | ≥ 11.0.0&&< 11.5.35 | 11.5.35composer require typo3/cms-core:^11.5.35 |
| 🐘Packagist | typo3/cms-core | ≥ 12.0.0&&< 12.4.11 | 12.4.11composer require typo3/cms-core:^12.4.11 |
| 🐘Packagist | typo3/cms-core | ≥ 13.0.0&&< 13.0.1 | 13.0.1composer require typo3/cms-core:^13.0.1 |
Affected Products
typo3typo3Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-core to 8.7.57 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-25119 is resolved across your whole dependency graph.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.
Frequently Asked Questions
Is CVE-2024-25119 in your dependencies?
Find it across Packagist, including transitive dependencies.