Skip to content
Fencer Intel
medium 5.7

CVE-2022-23504 json

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

published 3y ago modified 4mo ago also BIT-typo3-2022-23504 , EUVD-2022-7570 , GHSA-8w3p-qh3x-6gjr

cvss
5.7
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 46%
public exploits
0
none known

Summary

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.

Patch / fix

  • packagist typo3/cms-core 9.5.38, 10.4.33, 11.5.20, 12.1.1
  • packagist typo3/cms 10.4.33, 11.5.20, 12.1.1
  • bitnami typo3 9.5.38, 10.4.33, 11.5.20, 12.1.1
  • typo3 typo3 9.5.38, 10.4.33, 11.5.20, 12.1.1

Is CVE-2022-23504 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.55% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 5.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:L
GitHub 3.1 5.7 CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:L/A:L
NVD 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
OSV 3.1 4.9 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
packagist 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.38
10.4.33
11.5.20
12.1.1
packagist typo3/cms
>=10.0.0, <10.4.33
>=11.0.0, <11.5.20
>=12.0.0, <12.1.1
10.4.33
11.5.20
12.1.1
bitnami typo3
>=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.38
10.4.33
11.5.20
12.1.1

Affected products

  • TYPO3 typo3

Classification

Weakness
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-917 Improper Neutralization of Special Elements used in an Expression Language Statement

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.