Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist

GHSA-38r2-5695-334w

MEDIUMFix: TYPO3/typo3@1186b2f

GHSA-38r2-5695-334w is a medium-severity (CVSS 4.3) Information Exposure vulnerability in typo3/cms-core. O3 Security confirms whether GHSA-38r2-5695-334w is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

TYPO3 Backend Forms vulnerable to Information Disclosure of Hashed Passwords

Also known asCVE-2024-25118
Published
Feb 13, 2024
Updated
Feb 16, 2024
Affected
6 pkgs
Patched
6 / 6
Exploits
None indexed

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

Password hashes were being reflected in the editing forms of the TYPO3 backend user interface. This allowed attackers to crack the plaintext password using brute force techniques. Exploiting this vulnerability requires a valid backend user account.

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 the TYPO3 framework merger Christian Kuhn and external security researchers Maximilian Beckmann, Klaus-Günther Schmidt who reported this issue, and TYPO3 security team member Oliver Hader who fixed the issue.

References

Affected Packages

6 total 6 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagisttypo3/cms-core8.0.0&&< 8.7.578.7.57
🐘Packagisttypo3/cms-core9.0.0&&< 9.5.469.5.46
🐘Packagisttypo3/cms-core10.0.0&&< 10.4.4310.4.43
🐘Packagisttypo3/cms-core11.0.0&&< 11.5.3511.5.35
🐘Packagisttypo3/cms-core12.0.0&&< 12.4.1112.4.11
🐘Packagisttypo3/cms-core13.0.0&&< 13.0.113.0.1

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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  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-38r2-5695-334w is resolved across your whole dependency graph.

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

  4. How O3 protects you

    O3 pinpoints whether GHSA-38r2-5695-334w is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-38r2-5695-334w. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Problem Password hashes were being reflected in the editing forms of the TYPO3 backend user interface. This allowed attackers to crack the plaintext password using brute force techniques. Exploiting this vulnerability requires a valid backend user account. ### 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 the TYPO3 framework merger Christian Kuhn and external security researchers Maximilian Beckmann, Klaus-Günther Schmidt who reported this issue, and TYPO3 security team memb
O3 Security · Impact-Aware SCA

Is GHSA-38r2-5695-334w in your dependencies?

O3 detects GHSA-38r2-5695-334w across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.