High

TYPO3 is vulnerable to Cross-Site Scripting via frontend rendering

  • Disclosed: 08.02.2023
  • Updated: 11.10.2026 10:22

CVSS: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L/E:F/RL:O/RC:C (8.2)

Problem

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 into pages that have not yet been rendered and cached. 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.

  • GeneralUtility::getIndpEnv('PATH_INFO')
  • GeneralUtility::getIndpEnv('SCRIPT_NAME')
  • GeneralUtility::getIndpEnv('TYPO3_REQUEST_DIR')
  • GeneralUtility::getIndpEnv('TYPO3_REQUEST_SCRIPT')
  • GeneralUtility::getIndpEnv('TYPO3_SITE_PATH')
  • GeneralUtility::getIndpEnv('TYPO3_SITE_SCRIPT')
  • GeneralUtility::getIndpEnv('TYPO3_SITE_URL')

Installations of TYPO3 versions 8.7 and 9.x are probably only affected when server environment variable TYPO3_PATH_ROOT is defined - which is the case if they were installed via Composer.

Additional investigations confirmed that Apache and Microsoft IIS web servers using PHP-CGI (FPM, FCGI/FastCGI, or similar) are affected. There might be the risk that nginx is vulnerable as well. It was not possible to exploit Apache/mod_php scenarios.

Solution

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.

Update to TYPO3 versions 8.7.51 ELTS, 9.5.40 ELTS, 10.4.36 LTS, 11.5.23 LTS and 12.2.0 that fix the problem described above.

ℹ️ Strong security defaults - Manual actions required Any web server using PHP-CGI (FPM, FCGI/FastCGI, or similar) needs to ensure that the PHP setting cgi.fix_pathinfo=1 is used, which is the default PHP setting. In case this setting is not enabled, an exception is thrown to avoid continuing with invalid path information.

For websites that cannot be patched timely the TypoScript setting config.absRefPrefix at least should be set to a static path value, instead of using auto - e.g. config.absRefPrefix=/ - this does not fix all aspects of the vulnerability, and is just considered to be an intermediate mitigation to the most prominent manifestation.

References

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package 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
Composer package 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

References

CVSS score 8.8/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L
Weakness (CWE)
CWE-79
Platform
Composer
Package
typo3/cms, typo3/cms-core
Disclosed
08.02.2023
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-r4f8-f93x-5qh3 - CC BY 4.0

Vulnerability history: typo3/cms

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (188) in the archive
Total entries
188
First → latest
09.2018 06.2024
Without a fix
3
Exploited in attacks
0

Severity breakdown

  • Critical 6
  • High 41
  • Medium 128
  • Low 13

Disclosures per year

  1. 2018: 2
  2. 2019: 0
  3. 2020: 13
  4. 2021: 15
  5. 2022: 85
  6. 2023: 1
  7. 2024: 72
  8. 2025: 0
  9. 2026: 0
Severity:
  1. High · 8.1 ghsa-f777-f784-36gm >= 7.0.0, < 7.6.32, >= 8.0.0, < 8.7.21, >= 9.0.0, < 9.5.2 7.6.32, 8.7.21, 9.5.2
  2. High · 8.8 ghsa-8h4m-r4wm-xj7r >= 8.0.0, < 8.7.23, >= 9.0.0, < 9.5.4 8.7.23, 9.5.4
  3. High · 7.5 ghsa-g585-crjf-vhwq >= 7.0.0, < 7.6.32, >= 8.0.0, < 8.7.21 7.6.32, 8.7.21
  4. High · 7.3 ghsa-c5mj-39cf-3pp5 >= 8.0.0, < 8.7.23, >= 9.0.0, < 9.5.4 8.7.23, 9.5.4
  5. High · 8.1 ghsa-hh95-5xm5-v8v7 >= 8.0.0, < 8.7.30, >= 9.0.0, < 9.5.12 8.7.30, 9.5.12
  6. High ghsa-ppgf-8745-8pgx >= 7.0.0, < 7.6.30, >= 8.0.0, < 8.7.17, >= 9.0.0, < 9.3.2 7.6.30, 8.7.17, 9.3.2
  7. High · 8.8 ghsa-7qwg-fcpw-xg5g >= 8.5.0, < 8.7.17, >= 9.0.0, < 9.3.2 8.7.17, 9.3.2
  8. High ghsa-g4pf-3jvq-2gcw >= 6.2.0, < 6.2.30, >= 7.6.0, < 7.6.15, >= 8.0.0, < 8.5.1 6.2.30, 7.6.15, 8.5.1
  9. Critical · 9.9 ghsa-67wg-6j7r-mqh8 >= 7.6.0, < 7.6.22, >= 8.0.0, < 8.7.5 7.6.22, 8.7.5
  10. High ghsa-8h28-f46f-m87h >= 8.5.0, < 8.7.17, >= 9.0.0, < 9.3.2 8.7.17, 9.3.2
  11. Critical · 9.0 ghsa-gwfx-p7mr-f92v >= 6.2.0, < 6.2.25, >= 7.6.0, < 7.6.8, >= 8.0.0, < 8.1.1 6.2.25, 7.6.8, 8.1.1
  12. High ghsa-qffc-gwpp-m2xr >= 6.2.0, < 6.2.19, >= 7.6.0, < 7.6.4 6.2.19, 7.6.4
  13. High ghsa-9895-53fc-98v2 >= 6.2.0, < 6.2.18 6.2.18
  14. High · 7.1 ghsa-r9vc-jfmh-6j48 >= 6.2.0, < 6.2.14, >= 7.0.0, < 7.3.1 6.2.14, 7.3.1
  15. High · 8.8 ghsa-4r76-xr68-w7m7 >= 6.2.0, < 6.2.14, >= 7.0.0, < 7.3.1 6.2.14, 7.3.1
  16. High ghsa-p84g-j2gh-83g3 >= 6.2.0, < 6.2.9, >= 7.0.0, < 7.0.2 6.2.9, 7.0.2
  17. High · 8.1 ghsa-45xg-4w5x-j429 >= 6.2.0, < 6.2.6, >= 6.1.0, < 6.1.12, >= 4.7.0, < 4.7.20, >= 4.5.0, < 4.5.37 6.2.6, 6.1.12, 4.7.20, 4.5.37
  18. TYPO3 is vulnerable to Cross-Site Scripting via frontend rendering this entry
    High · 8.8 CVE-2023-24814 >= 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
  19. Critical · 9.8 CVE-2022-47406 < 2.0.5, >= 3.0.0, < 3.0.3 2.0.5, 3.0.3
  20. High · 7.5 CVE-2022-23503 >= 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
  21. High · 8.8 CVE-2019-12747 >= 8.0.0, < 8.7.27, >= 9.0.0, < 9.5.8 8.7.27, 9.5.8
  22. High · 7.5 CVE-2019-11832 >= 8.0.0, < 8.7.25, >= 9.0.0, < 9.5.6 8.7.25, 9.5.6
  23. High · 8.8 CVE-2019-19849 >= 10.0.0, < 10.2.1, >= 8.0.0, < 8.7.30, >= 9.0.0, < 9.5.12 10.2.1, 8.7.30, 9.5.12
  24. High CVE-2010-3714 >= 4.2.0, < 4.2.15, >= 4.3.0, < 4.3.7, >= 4.4.0, < 4.4.4 4.2.15, 4.3.7, 4.4.4
  25. High CVE-2013-4321 >= 6.0.0, < 6.0.9, >= 6.1.0, < 6.1.4 6.0.9, 6.1.4
  26. High CVE-2013-4250 >= 6.0.0, < 6.0.8, >= 6.1.0, < 6.1.3 6.0.8, 6.1.3
  27. High CVE-2014-9509 >= 4.5.0, < 4.5.39, >= 6.2.0, < 6.2.9, >= 7.0.0, < 7.0.2, >= 4.6.0, < 4.6.19, >= 4.7.0, < 4.7.21, >= 6.0.0, < 6.0.15, >= 6.1.0, < 6.1.13 4.5.39, 6.2.9, 7.0.2, 4.6.19, 4.7.21, 6.0.15, 6.1.13
  28. High CVE-2013-4701 >= 6.2.0, < 6.2.6 6.2.6
  29. High · 8.8 CVE-2017-14251 >= 7.6.0, < 7.6.22, >= 8.0.0, < 8.7.5 7.6.22, 8.7.5
  30. High CVE-2014-3942 >= 4.5.0, < 4.5.34, >= 4.7.0, < 4.7.19, >= 6.0.0, < 6.0.14, >= 6.1.0, < 6.1.9 4.5.34, 4.7.19, 6.0.14, 6.1.9
  31. High CVE-2010-1153 >= 4.3.0, < 4.3.3 4.3.3
  32. High CVE-2009-0258 >= 4.0.0, < 4.0.10, >= 4.1.0, < 4.1.8, >= 4.2.0, < 4.2.4 4.0.10, 4.1.8, 4.2.4
  33. High CVE-2009-0256 >= 4.0.0, < 4.0.10, >= 4.1.0, < 4.1.8, >= 4.2.0, < 4.2.4 4.0.10, 4.1.8, 4.2.4
  34. Critical · 9.8 CVE-2011-3583 >= 4.5.0, <= 4.5.5 no fix
  35. Critical · 9.8 CVE-2011-4628 < 4.3.12, >= 4.4.0, < 4.4.9, >= 4.5.0, < 4.5.4 4.3.12, 4.4.9, 4.5.4
  36. High · 8.8 CVE-2021-41113 >= 11.2.0, < 11.5.0 11.5.0
  37. High · 8.3 CVE-2021-21357 >= 10.0.0, < 10.4.14, >= 11.0.0, < 11.1.1, >= 9.0.0, < 9.5.25 10.4.14, 11.1.1, 9.5.25
  38. High · 8.6 CVE-2021-21355 >= 10.0.0, < 10.4.14, >= 11.0.0, < 11.1.1, >= 9.0.0, < 9.5.25 10.4.14, 11.1.1, 9.5.25
  39. High · 8.1 CVE-2020-26228 >= 10.0.0, < 10.4.10, >= 9.0.0, < 9.5.23, >= 8.7.0, < 8.7.38 10.4.10, 9.5.23, 8.7.38
  40. High · 8.1 CVE-2020-15099 >= 10.0.0, < 10.4.6, >= 9.0.0, < 9.5.20 10.4.6, 9.5.20
  41. High · 8.8 CVE-2020-15098 >= 10.0.0, < 10.4.6, >= 9.0.0, < 9.5.20 10.4.6, 9.5.20
  42. High · 8.0 CVE-2020-11069 >= 10.0.0, < 10.4.2, >= 9.0.0, < 9.5.17 10.4.2, 9.5.17
  43. High · 8.8 CVE-2020-11067 >= 10.0.0, < 10.4.2, >= 9.0.0, < 9.5.17 10.4.2, 9.5.17
  44. High · 8.7 CVE-2020-11066 >= 10.0.0, < 10.4.2, >= 9.0.0, < 9.5.17 10.4.2, 9.5.17
  45. High · 7.1 CVE-2019-10912 >= 9.0.0, < 9.5.8 9.5.8

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.