TYPO3 Cross-Site Scripting Vulnerability in typolinks
Summary
GHSA-75mx-chcf-2q32: TYPO3 Cross-Site Scripting vulnerability in typolinks. Affects typo3/cms across 2 version ranges.
>= 6.2.0, < 6.2.16
>= 7.0.0, < 7.6.1
Fixed in 6.2.16 or 7.6.1, depending on the release line you run. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
Background
TYPO3 is an open-source content management system (CMS) used for building and managing websites. The TYPO3 CMS package, available on Packagist, is vulnerable to a Cross-Site Scripting (XSS) attack. This vulnerability affects all link fields within the TYPO3 installation, allowing authorized editors to insert malicious JavaScript commands using the javascript: URL scheme.
Vulnerability Detail
The Cross-Site Scripting vulnerability in TYPO3 CMS allows attackers to inject and execute arbitrary JavaScript code within the context of a user's browser. This can lead to various security risks, such as session hijacking, defacement of web pages, theft of sensitive information, or even complete compromise of the affected TYPO3 installation. The vulnerability has a CVSS score of 6.1, indicating a moderate severity level.
How To Fix
Fixed versions by release line
The minimum fixed version depends on the release line you run.
-
>= 6.2.0, < 6.2.166.2.16composer require typo3/cms:6.2.16 -
>= 7.0.0, < 7.6.17.6.1composer require typo3/cms:7.6.1
Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →
Workaround
As a temporary workaround, users can sanitize and validate user input before storing or rendering it in link fields within TYPO3 CMS. This can be achieved by implementing proper input validation and output encoding techniques. Here is an example of how to sanitize user input in PHP:
$input = $_POST['link_field'];
$sanitizedInput = htmlspecialchars($input);
Conclusion
The TYPO3 CMS package is vulnerable to a Cross-Site Scripting (XSS) attack, allowing authorized editors to insert malicious JavaScript commands. To mitigate this vulnerability, TYPO3 CMS users should upgrade to the fixed versions of the package. In the meantime, implementing proper input validation and output encoding techniques can serve as a temporary workaround. For further support on vulnerability remediation, please contact DevNack.com.
See every vulnerability recorded for typo3/cms →
FAQ
TYPO3 CMS is an open-source content management system used for building and managing websites. It provides a flexible and extensible platform for creating web applications.
Cross-Site Scripting (XSS) is a type of security vulnerability that allows attackers to inject malicious scripts into web pages viewed by other users. This can lead to the execution of arbitrary code and various security risks.
The TYPO3 CMS XSS vulnerability allows authorized editors to insert JavaScript commands into link fields. When other users view these links, the injected JavaScript code is executed within their browsers, potentially leading to security breaches and unauthorized actions.
The TYPO3 CMS XSS vulnerability has a CVSS score of 6.1, indicating a moderate severity level.
You can use Vulert's playground at Vulert Scanner to check if your TYPO3 CMS installation is affected by this vulnerability. Vulert monitors and alerts in real-time for open-source vulnerabilities, using just the composer.lock file.
References
Related vulnerabilities
Recent vulnerabilities recorded for typo3/cms.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
