HTML injection via raw history record titles
Published May 14, 2024 · Updated Aug 2, 2024
HTML injection in TYPO3 CMS 13.0.0 through 13.1.0 allows remote authenticated users to place malicious markup in backend history views. The History.html template renders the title returned by BackendUtility::getRecordTitle as raw output even when that value was not HTML-encoded. A valid backend account and another user's viewing of the affected history entry are required; Content Security Policy prevents JavaScript execution, limiting impact to displayed markup.
Summary
What happened
HTML injection in TYPO3 CMS 13.0.0 through 13.1.0 allows remote authenticated users to place malicious markup in backend history views. The History.html template renders the title returned by BackendUtility::getRecordTitle as raw output even when that value was not HTML-encoded. A valid backend account and another user's viewing of the affected history entry are required; Content Security Policy prevents JavaScript execution, limiting impact to displayed markup.
The record
- CVE
- CVE-2024-34355
- Published
- May 14, 2024
- Updated
- Aug 2, 2024
- Vendor
- in2code GmbH
- Product
- TYPO3 CMS
- Classifications
- CWE-116, CWE-79
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 14, 2024CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 13.0.0, < 13.1.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo