TYPO3 vulnerable to an HTML Injection in the History Module
Problem
The history backend module is vulnerable to HTML injection. Although Content-Security-Policy headers effectively prevent JavaScript execution, adversaries can still inject malicious HTML markup. Exploiting this vulnerability requires a valid backend user account.
Solution
Update to TYPO3 version 13.1.1 that fixes the problem described.
Credits
Thanks to TYPO3 core team member Andreas Kienast who reported this issue and to TYPO3 core & security team Benjamin Franzke who fixed the issue.
References
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| Composer package | typo3/cms-core | >= 13.0.0, < 13.1.1 | 13.1.1 |
References
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N- Weakness (CWE)
CWE-116, CWE-79- Platform
- Composer
- Package
typo3/cms-core- Disclosed
- 14.05.2024
- Updated
- 11.10.2026 10:22
Sources and licenses
OSV / GitHub Advisory Database - GHSA-xjwx-78x7-q6jc - CC BY 4.0
Vulnerability history: typo3/cms-core
All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 128
- First → latest
- 09.2018 09.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 1
- High 35
- Medium 84
- Low 8
Disclosures per year
- 2018: 2
- 2019: 0
- 2020: 13
- 2021: 15
- 2022: 34
- 2023: 3
- 2024: 38
- 2025: 8
- 2026: 15
-
TYPO3 vulnerable to an HTML Injection in the History Module this entry
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.