Skip to content
Fencer Vulns
high 8.8

CVE-2023-24814 json

Persisted Cross-Site Scripting in Frontend Rendering in typo3

published 2023-02-07 3 y ago modified 2026-09-10 1 mo ago also BIT-typo3-2023-24814 , EUVD-2023-0784 , GHSA-r4f8-f93x-5qh3

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

Summary

TYPO3 is a free and open source Content Management Framework released under the GNU General Public License. In affected versions the TYPO3 core component `GeneralUtility::getIndpEnv()` uses the unfiltered server environment variable `PATH_INFO`, which allows attackers to inject malicious content. In combination with the TypoScript setting `config.absRefPrefix=auto`, attackers can inject malicious HTML code to pages that have not been rendered and cached, yet. As a result, injected values would be cached and delivered to other website visitors (persisted cross-site scripting). Individual code which relies on the resolved value of `GeneralUtility::getIndpEnv('SCRIPT_NAME')` and corresponding usages (as shown below) are vulnerable as well. Additional investigations confirmed that at least Apache web server deployments using CGI (FPM, FCGI/FastCGI, and similar) are affected. However, there still might be the risk that other scenarios like nginx, IIS, or Apache/mod_php are vulnerable. The usage of server environment variable `PATH_INFO` has been removed from corresponding processings in `GeneralUtility::getIndpEnv()`. Besides that, the public property `TypoScriptFrontendController::$absRefPrefix` is encoded for both being used as a URI component and for being used as a prefix in an HTML context. This mitigates the cross-site scripting vulnerability. Users are advised to update to TYPO3 versions 8.7.51 ELTS, 9.5.40 ELTS, 10.4.35 LTS, 11.5.23 LTS and 12.2.0 which fix this problem. For users who are unable to patch in a timely manner the TypoScript setting `config.absRefPrefix` should at least be set to a static path value, instead of using auto - e.g. `config.absRefPrefix=/`. This workaround **does not fix all aspects of the vulnerability**, and is just considered to be an intermediate mitigation to the most prominent manifestation.

Patch / fix

  • packagist typo3/cms-core 8.7.51, 9.5.40, 10.4.36, 11.5.23, 12.2.0
  • packagist typo3/cms 10.4.35, 11.5.23, 12.2.0
  • bitnami typo3 9.5.40, 9.7.51, 10.4.36, 11.5.23, 12.2.0
  • typo3 typo3 9.5.40, 9.7.51, 10.4.36, 11.5.23, 12.2.0

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
20 mo ago

Exploit prediction

0.83% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/TYPO3/typo3/security/advisories/GHSA-r4f8-f93x-5qh3 referenced PoC, tagged "exploit" by a source, unverified
  • typo3.org https://typo3.org/security/advisory/typo3-core-sa-2023-001 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Affected packages

ecosystem package affected fixed in
packagist typo3/cms-core
>=12.0.0, <12.2.0
>=11.0.0, <11.5.23
>=10.0.0, <10.4.36
>=9.0.0, <9.5.40
>=8.7.0, <8.7.51
12.2.0
11.5.23
10.4.36
9.5.40
8.7.51
packagist typo3/cms
>=10.0.0, <10.4.35
>=11.0.0, <11.5.23
>=12.0.0, <12.2.0
10.4.35
11.5.23
12.2.0
bitnami typo3
>=8.7.0, <9.7.51
>=9.0.0, <9.5.40
>=10.0.0, <10.4.36
>=11.0.0, <11.5.23
>=12.0.0, <12.2.0
9.7.51
9.5.40
10.4.36
11.5.23
12.2.0

Affected products

  • TYPO3 typo3

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

References

Sources

Fencer Vulns 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.