TYPO3 Cross-Site Scripting Vulnerability Exploitable by Editors
Published 30 May 2024 · Updated 5 Dec 2024
Affected packages
- Affected
- >=6.2.0 <6.2.14
- Fixed in
- 6.2.14
composer require typo3/cms:^6.2.14- Affected
- >=7.0.0 <7.3.1
- Fixed in
- 7.3.1
composer require typo3/cms:^7.3.1Details
It has been discovered that link tags generated by typolink functionality in the website's frontend are vulnerable to cross-site scripting - values being assigned to HTML attributes have not been parsed correctly. A valid backend user account is needed to exploit this vulnerability.
As second and separate vulnerability in the filelist module of the backend user interface has been referenced with this advisory as well. Error messages being shown after using a malicious name for renaming a file are not propery encoded, thus vulnerable to cross-site scripting. A valid backend user account is needed to exploit this vulnerability.
Is GHSA-wp8j-c736-c5r3 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
- Linkgithub.com/TYPO3/typo3/commit/7695d91fca1a96a3a3e7466097ae92c32b1130d8
- Linkgithub.com/TYPO3/typo3/commit/d7feb40c8d277c6b6ab3a548313be1e1a2084299
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2015-07-01-3.yaml
- Packagegithub.com/TYPO3/typo3
- Linktypo3.org/security/advisory/typo3-core-sa-2015-004
- Linktypo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2015-004
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.