MediumGHSA-xgmx-j3hv-jh9x
TYPO3 Cross-Site Scripting in Link Handling
Published 7 Jun 2024 · Updated 4 Dec 2024
Affected packages
typo3/cmsComposer
- Affected
- >=10.0.0 <10.2.1
- Fixed in
- 10.2.1
Update to the fixed version for your release line, for example:
composer require typo3/cms:^10.2.1typo3/cmsComposer
- Affected
- >=8.0.0 <8.7.30
- Fixed in
- 8.7.30
Update to the fixed version for your release line, for example:
composer require typo3/cms:^8.7.30typo3/cmsComposer
- Affected
- >=9.0.0 <9.5.12
- Fixed in
- 9.5.12
Update to the fixed version for your release line, for example:
composer require typo3/cms:^9.5.12Details
It has been discovered that t3:// URL handling and typolink functionality are vulnerable to cross-site scripting. Not only regular backend forms are affected but also frontend extensions which use the rendering with typolink.
Is GHSA-xgmx-j3hv-jh9x 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/25f796b94e23bac77e836bd38f53ce998c094901
- Linkgithub.com/TYPO3/typo3/commit/64db88b9b61bb67b3b44145dc8e0e1ef251da45e
- Linkgithub.com/TYPO3/typo3/commit/a35c42e9bcb020e16016d1c146354513a9856bc0
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2019-12-17-2.yaml
- Packagegithub.com/TYPO3/typo3
- Linktypo3.org/security/advisory/typo3-core-sa-2019-022
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.