Cross-Site Scripting in TYPO3 CMS Form Engine
Published 13 May 2020 · Updated 8 Jul 2026
Affected packages
- Affected
- >=9.0.0 <9.5.17
- Fixed in
- 9.5.17
composer require typo3/cms-core:^9.5.17- Affected
- >=10.0.0 <10.4.2
- Fixed in
- 10.4.2
composer require typo3/cms-core:^10.4.2- Affected
- >=10.0.0 <10.4.2
- Fixed in
- 10.4.2
composer require typo3/cms:^10.4.2- Affected
- >=9.0.0 <9.5.17
- Fixed in
- 9.5.17
composer require typo3/cms:^9.5.17Details
In TYPO3 CMS greater than or equal to 9.0.0 and less than 9.5.17 and greater than or equal to 10.0.0 and less than 10.4.2, it has been discovered that HTML placeholder attributes containing data of other database records are vulnerable to cross-site scripting. A valid backend user account is needed to exploit this vulnerability.
Update to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.
References
- https://typo3.org/security/advisory/typo3-core-sa-2020-002
Is GHSA-43gj-mj2w-wh46 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/TYPO3.CMS/security/advisories/GHSA-43gj-mj2w-wh46
- Advisorynvd.nist.gov/vuln/detail/CVE-2020-11064
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2020-11064.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2020-11064.yaml
- Linktypo3.org/security/advisory/typo3-core-sa-2020-002
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.