# CVE-2023-24814: Persisted Cross-Site Scripting in Frontend Rendering in typo3 > Attackers can inject malicious HTML into cached pages via PATH_INFO, leading to persisted XSS for other visitors in TYPO3. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:H/A:L`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 7 Feb 2023 - **Updated:** 10 Mar 2025 - **Also known as:** BIT-typo3-2023-24814, GHSA-r4f8-f93x-5qh3 ## What is CVE-2023-24814? CVE-2023-24814 is a high-severity cross-site scripting vulnerability in Typo3 Typo3, published on 7 Feb 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description 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. Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation) ## Which versions are affected by CVE-2023-24814? 17 open source packages ship an affected version, including typo3/cms-core, typo3 and typo3/cms. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `typo3/cms-core` | Packagist | From 10.0.0 | 10.4.36 | | `typo3/cms-core` | Packagist | From 10.0.0 | 10.4.36 | | `typo3/cms-core` | Packagist | From 11.0.0 | 11.5.23 | | `typo3/cms-core` | Packagist | From 11.0.0 | 11.5.23 | | `typo3/cms-core` | Packagist | From 12.0.0 | 12.2.0 | | `typo3/cms-core` | Packagist | From 12.0.0 | 12.2.0 | | `typo3/cms-core` | Packagist | From 8.7.0 | 8.7.51 | | `typo3/cms-core` | Packagist | From 8.7.0 | 8.7.51 | | `typo3/cms-core` | Packagist | From 9.0.0 | 9.5.40 | | `typo3/cms-core` | Packagist | From 9.0.0 | 9.5.40 | | `typo3` | Bitnami | From 8.7.0 | 9.7.51, 9.5.40, 10.4.36, 11.5.23, 12.2.0 | | `typo3/cms` | Packagist | From 10.0.0 | 10.4.35 | | `typo3/cms` | Packagist | From 10.0.0 | 10.4.35 | | `typo3/cms` | Packagist | From 11.0.0 | 11.5.23 | | `typo3/cms` | Packagist | From 11.0.0 | 11.5.23 | | `typo3/cms` | Packagist | From 12.0.0 | 12.2.0 | | `typo3/cms` | Packagist | From 12.0.0 | 12.2.0 | Products: Typo3 Typo3. ## How do I fix CVE-2023-24814? Upgrade typo3/cms-core to a fixed version for your release line: 10.4.36, 11.5.23, 12.2.0 or 8.7.51. ## Is CVE-2023-24814 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24814 exists. ## Other vulnerabilities in Typo3 Typo3 - [CVE-2009-0258](https://insights.sbomify.com/CVE-2009-0258/): Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection (critical 10.0) - [CVE-2011-3583](https://insights.sbomify.com/CVE-2011-3583/): Typo3 SQL injection due to faulty prepared statements (critical 9.8) - [CVE-2011-4628](https://insights.sbomify.com/CVE-2011-4628/): Typo3 Authentication Bypass (critical 9.8) - [CVE-2021-41113](https://insights.sbomify.com/CVE-2021-41113/): Cross-Site-Request-Forgery in Backend URI Handling in Typo3 (high 8.8) - [CVE-2020-15098](https://insights.sbomify.com/CVE-2020-15098/): Missing Required Cryptographic Step Leading to Sensitive Information Disclosure in TYPO3 CMS (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-24814 and fix it if it is affected. What it is: CVE-2023-24814 is a high-severity cross-site scripting vulnerability in Typo3 Typo3, published on 7 Feb 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24814 exists. Affected packages and fixed versions: - typo3/cms-core (Packagist): affected from 10.0.0; fixed in 10.4.36 - typo3/cms-core (Packagist): affected from 10.0.0; fixed in 10.4.36 - typo3/cms-core (Packagist): affected from 11.0.0; fixed in 11.5.23 - typo3/cms-core (Packagist): affected from 11.0.0; fixed in 11.5.23 - typo3/cms-core (Packagist): affected from 12.0.0; fixed in 12.2.0 - typo3/cms-core (Packagist): affected from 12.0.0; fixed in 12.2.0 - typo3/cms-core (Packagist): affected from 8.7.0; fixed in 8.7.51 - typo3/cms-core (Packagist): affected from 8.7.0; fixed in 8.7.51 - typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.5.40 - typo3/cms-core (Packagist): affected from 9.0.0; fixed in 9.5.40 - typo3 (Bitnami): affected from 8.7.0; fixed in 9.7.51, 9.5.40, 10.4.36, 11.5.23, 12.2.0 - typo3/cms (Packagist): affected from 10.0.0; fixed in 10.4.35 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-24814/ (Markdown: https://insights.sbomify.com/CVE-2023-24814/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-24814 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-24814 - OSV: https://osv.dev/vulnerability/CVE-2023-24814 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-24814/ Summaries are generated and may contain mistakes; the official description above is the record.