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

CVE-2022-23504

MEDIUM

CVE-2022-23504 is a medium-severity (CVSS 5.7) Information Exposure vulnerability in typo3/cms-core. O3 Security confirms whether CVE-2022-23504 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

TYPO3 contains Sensitive Information Disclosure via YAML Placeholder Expressions in Site Configuration

Also known asBIT-typo3-2022-23504GHSA-8w3p-qh3x-6gjr
Published
Dec 14, 2022
Updated
Aug 7, 2026
Affected
7 pkgs
Patched
7 / 7
Exploits
None indexed

Blast Radius

7 pkgs affected
🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms🐘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

TYPO3 is an open source PHP based web content management system. Versions prior to 9.5.38, 10.4.33, 11.5.20, and 12.1.1 are subject to Sensitive Information Disclosure. Due to the lack of handling user-submitted YAML placeholder expressions in the site configuration backend module, attackers could expose sensitive internal information, such as system configuration or HTTP request messages of other website visitors. A valid backend user account having administrator privileges is needed to exploit this vulnerability. This issue has been patched in versions 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1.

Affected Packages

7 total 7 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagisttypo3/cms-core9.0.0&&< 9.5.389.5.38
🐘Packagisttypo3/cms-core10.0.0&&< 10.4.3310.4.33
🐘Packagisttypo3/cms-core11.0.0&&< 11.5.2011.5.20
🐘Packagisttypo3/cms-core12.0.0&&< 12.1.112.1.1
🐘Packagisttypo3/cms10.0.0&&< 10.4.3310.4.33
🐘Packagisttypo3/cms11.0.0&&< 11.5.2011.5.20

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 9.5.38 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-23504 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 CVE-2022-23504 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 CVE-2022-23504. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

TYPO3 is an open source PHP based web content management system. Versions prior to 9.5.38, 10.4.33, 11.5.20, and 12.1.1 are subject to Sensitive Information Disclosure. Due to the lack of handling user-submitted YAML placeholder expressions in the site configuration backend module, attackers could expose sensitive internal information, such as system configuration or HTTP request messages of other website visitors. A valid backend user account having administrator privileges is needed to exploit this vulnerability. This issue has been patched in versions 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1.
O3 Security · Impact-Aware SCA

Is CVE-2022-23504 in your dependencies?

O3 detects CVE-2022-23504 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.