MediumGHSA-w3v6-r62r-fvqhCVE-2012-1608
Typo3 API XSS Vulnerabilities
Published 17 May 2022 · Updated 8 Nov 2023
Affected packages
typo3/cmsComposer
- Affected
- >=4.4.0 <4.4.14
- Fixed in
- 4.4.14
Update to the fixed version for your release line, for example:
composer require typo3/cms:^4.4.14typo3/cmsComposer
- Affected
- >=4.5.0 <4.5.14
- Fixed in
- 4.5.14
Update to the fixed version for your release line, for example:
composer require typo3/cms:^4.5.14typo3/cmsComposer
- Affected
- >=4.6.0 <4.6.7
- Fixed in
- 4.6.7
Update to the fixed version for your release line, for example:
composer require typo3/cms:^4.6.7Details
The t3lib_div::RemoveXSS API method in TYPO3 4.4.0 through 4.4.13, 4.5.0 through 4.5.13, 4.6.0 through 4.6.6, 4.7, and 6.0 allows remote attackers to bypass the cross-site scripting (XSS) protection mechanism and inject arbitrary web script or HTML via non printable characters.
Is GHSA-w3v6-r62r-fvqh in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.