MediumGHSA-g4c9-qfvw-fmr4
TYPO3 Cross-Site Scripting in Backend Modal Component
Published 30 May 2024 · Updated 5 Dec 2024
Affected packages
typo3/cms-coreComposer
- Affected
- >=8.0.0 <8.7.21
- Fixed in
- 8.7.21
Update to the fixed version for your release line, for example:
composer require typo3/cms-core:^8.7.21typo3/cms-coreComposer
- Affected
- >=9.0.0 <9.5.2
- Fixed in
- 9.5.2
Update to the fixed version for your release line, for example:
composer require typo3/cms-core:^9.5.2typo3/cms-coreComposer
- Affected
- >=7.1.0 <7.6.32
- Fixed in
- 7.6.32
Update to the fixed version for your release line, for example:
composer require typo3/cms-core:^7.6.32Details
Failing to properly encode user input, notifications shown in modal windows in the TYPO3 backend are vulnerable to cross-site scripting. A valid backend user account is needed in order to exploit this vulnerability.
Is GHSA-g4c9-qfvw-fmr4 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-core, and gives you the command that fixes it.
References
- Linkgithub.com/TYPO3-CMS/core/commit/3c1deac4db61ac1ac4231799beb1f49c28eb2b4d
- Linkgithub.com/TYPO3-CMS/core/commit/983ecc4ea3a841aca7ff2bb1d2f0e0318c3646b3
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/2018-12-11-2.yaml
- Packagegithub.com/TYPO3-CMS/core
- Linktypo3.org/security/advisory/typo3-core-sa-2018-007
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.