Cross-Site Scripting in Content Preview
Published 23 Mar 2021 · Updated 8 Jul 2026
Affected packages
- Affected
- >=10.0.0 <10.4.14
- Fixed in
- 10.4.14
composer require typo3/cms-backend:^10.4.14- Affected
- >=11.0.0 <11.1.1
- Fixed in
- 11.1.1
composer require typo3/cms-backend:^11.1.1- Affected
- >=10.0.0 <10.4.14
- Fixed in
- 10.4.14
composer require typo3/cms-core:^10.4.14- Affected
- >=11.0.0 <11.1.1
- Fixed in
- 11.1.1
composer require typo3/cms-core:^11.1.1- Affected
- >=10.0.0 <10.4.14
- Fixed in
- 10.4.14
composer require typo3/cms:^10.4.14- Affected
- >=11.0.0 <11.1.1
- Fixed in
- 11.1.1
composer require typo3/cms:^11.1.1Details
Problem
It has been discovered that database fields used as _descriptionColumn_ are vulnerable to cross-site scripting when their content gets previewed in the page module. A valid backend user account is needed to exploit this vulnerability.
Solution
Update to TYPO3 versions 10.4.14, 11.1.1 that fix the problem described.
Credits
Thanks to Richie Lee who reported this issue and to TYPO3 framework merger Andreas Fernandez who fixed the issue.
References
Is GHSA-fjh3-g8gq-9q92 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-backend, and gives you the command that fixes it.
References
- Linkgithub.com/TYPO3/TYPO3.CMS/security/advisories/GHSA-fjh3-g8gq-9q92
- Advisorynvd.nist.gov/vuln/detail/CVE-2021-21340
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2021-21340.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2021-21340.yaml
- Linkpackagist.org/packages/typo3/cms-backend
- Linktypo3.org/security/advisory/typo3-core-sa-2021-007
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.