# CVE-2023-47125: By-passing Cross-Site Scripting Protection in HTML Sanitizer

> An attacker can bypass XSS protections in the TYPO3 HTML Sanitizer library by exploiting incorrect DOM processing instruction handling.

- **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **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:** 14 Nov 2023
- **Updated:** 29 Aug 2024
- **Also known as:** BIT-typo3-2023-47125, GHSA-mm79-jhqm-9j54

## What is CVE-2023-47125?

CVE-2023-47125 is a medium-severity cross-site scripting vulnerability in Typo3 Typo3, published on 14 Nov 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 an open source PHP based web content management system released under the GNU GPL. In affected versions DOM processing instructions are not handled correctly. This allows bypassing the cross-site scripting mechanism of typo3/html-sanitizer. This vulnerability has been addressed in versions 1.5.3 and 2.1.4. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2023-47125?

5 open source packages ship an affected version, including typo3/html-sanitizer and typo3. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/html-sanitizer` | Packagist | From 1.0.0 | 1.5.3 |
| `typo3/html-sanitizer` | Packagist | From 1.0.0 | 1.5.3 |
| `typo3/html-sanitizer` | Packagist | From 2.0.0 | 2.1.4 |
| `typo3/html-sanitizer` | Packagist | From 2.0.0 | 2.1.4 |
| `typo3` | Bitnami | From 8.7.42 | 8.7.55, 9.5.44, 10.4.41, 11.5.33, 12.4.8 |

Products: Typo3 Html Sanitizer, Typo3 Typo3.

## How do I fix CVE-2023-47125?

Upgrade typo3/html-sanitizer to a fixed version for your release line: 1.5.3 or 2.1.4.

## Is CVE-2023-47125 being exploited?

There is no known exploitation of CVE-2023-47125 in the wild and no public exploit code.

Public exploit code:

- Stored XSS (exploit) in TYPO3 HTML Sanitizer (CVE-2023-47125). DOM processing instructions are not handled correctly. This allows bypassing the cross-site scripting mechanism of typo3/html-sanitizer. (github_poc): https://github.com/nikn0laty/TYPO3-HTML-Sanitizer-XSS-CVE-2023-47125

## Other vulnerabilities in Typo3 Typo3

- [CVE-2022-23499](https://insights.sbomify.com/CVE-2022-23499/): Cross-Site Scripting Protection bypass in HTML Sanitizer (medium 6.1)
- [CVE-2022-36020](https://insights.sbomify.com/CVE-2022-36020/): Bypass of Cross-Site Scripting Protection in typo3/html-sanitizer (medium 6.1)
- [CVE-2023-38500](https://insights.sbomify.com/CVE-2023-38500/): By-passing Cross-Site Scripting Protection in HTML Sanitizer (medium 4.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-47125 and fix it if it is affected.

What it is: CVE-2023-47125 is a medium-severity cross-site scripting vulnerability in Typo3 Typo3, published on 14 Nov 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: There is no known exploitation of CVE-2023-47125 in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/html-sanitizer (Packagist): affected from 1.0.0; fixed in 1.5.3
- typo3/html-sanitizer (Packagist): affected from 1.0.0; fixed in 1.5.3
- typo3/html-sanitizer (Packagist): affected from 2.0.0; fixed in 2.1.4
- typo3/html-sanitizer (Packagist): affected from 2.0.0; fixed in 2.1.4
- typo3 (Bitnami): affected from 8.7.42; fixed in 8.7.55, 9.5.44, 10.4.41, 11.5.33, 12.4.8

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-47125/ (Markdown: https://insights.sbomify.com/CVE-2023-47125/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-47125
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-47125
- OSV: https://osv.dev/vulnerability/CVE-2023-47125

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-47125/
Summaries are generated and may contain mistakes; the official description above is the record.