Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2022-23504

TYPO3-CORE-SA-2022-016: Sensitive Information Disclosure via YAML Placeholder Expressions in Site Configuration

Overview

Published
14 Dec 2022
Modified
17 Jun 2026
Medium CVE
2 Registry packages
0 OS packages
0 Linux distributions
Yes Fix available

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.

Source: OX vulnerability database

Severity

4.9 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Weakness: CWE-200, CWE-917

Affected packages · 2

Packages affected by CVE-2022-23504
EcosystemPackageVulnerableFixed in
Composer (PHP) typo3/cms >=10.0.0, <10.4.33>=11.0.0, <11.5.20>=12.0.0, <12.1.1 10.4.3311.5.2012.1.1
Composer (PHP) typo3/cms-core >=9.0.0, <9.5.38>=10.0.0, <10.4.33>=11.0.0, <11.5.20>=12.0.0, <12.1.1 9.5.3810.4.3311.5.2012.1.1

Open a package to see all its vulnerabilities.

Operating systems

No Linux distribution reports this ID.

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.