Skip to content

TYPO3 vulnerable to an HTML Injection in the History Module

Low severity GitHub Reviewed Published May 14, 2024 in TYPO3/typo3 • Updated May 14, 2024

Package

composer typo3/cms-core (Composer)

Affected versions

>= 13.0.0, <= 13.1.0

Patched versions

13.1.1

Description

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

References

@ohader ohader published to TYPO3/typo3 May 14, 2024
Published by the National Vulnerability Database May 14, 2024
Published to the GitHub Advisory Database May 14, 2024
Reviewed May 14, 2024
Last updated May 14, 2024

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N

EPSS score

0.045%
(17th percentile)

Weaknesses

CVE ID

CVE-2024-34355

GHSA ID

GHSA-xjwx-78x7-q6jc

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.