NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

TYPO3 Install Tool vulnerable to Information Disclosure of Encryption KeyGHSA-h47m-3f78-qp9g

MEDIUMFix: TYPO3/typo3@14d1013

GHSA-h47m-3f78-qp9g 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.

Also known asCVE-2024-25119
Published
Updated
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed
Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 GHSA-h47m-3f78-qp9g.

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs30th percentile — riskier than 30% of all scored CVEsHighest risk
0.00%0.29%0.58%0.86%0.3%0.4%May 26Sep 26Nov 26

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

6 pkgs affected
🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core

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

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.

Solution

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.

Credits

Thanks to TYPO3 core & security team member Benjamin Franzke who fixed the issue.

References

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagisttypo3/cms-core≥ 8.0.0&&< 8.7.578.7.57composer require typo3/cms-core:^8.7.57
🐘Packagisttypo3/cms-core≥ 9.0.0&&< 9.5.469.5.46composer require typo3/cms-core:^9.5.46
🐘Packagisttypo3/cms-core≥ 10.0.0&&< 10.4.4310.4.43composer require typo3/cms-core:^10.4.43
🐘Packagisttypo3/cms-core≥ 11.0.0&&< 11.5.3511.5.35composer require typo3/cms-core:^11.5.35
🐘Packagisttypo3/cms-core≥ 12.0.0&&< 12.4.1112.4.11composer require typo3/cms-core:^12.4.11
🐘Packagisttypo3/cms-core≥ 13.0.0&&< 13.0.113.0.1composer require typo3/cms-core:^13.0.1

Affected Products

1 product · 6 configurations
Application
typo3typo3
≥ 12.0.0 && < 12.4.11
1 version
13.0.0

Detection & mitigation playbook

Open-source dependency

  1. Detect

    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.

  2. 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 GHSA-h47m-3f78-qp9g is resolved across your whole dependency graph.

  3. 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

### Problem 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. ### Solution 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. ### Credits Thanks to TYPO3 core & security team
O3 Security · Impact-Aware SCA

Is GHSA-h47m-3f78-qp9g in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
TYPO3 Install Tool vulnerable to Information Disclosure of…