Cross-Site Scripting in TYPO3's Form Framework
Published 17 Jun 2022 · Updated 6 Dec 2023
Affected packages
- Affected
- >=8.0.0 <8.7.47
- Fixed in
- 8.7.47
composer require typo3/cms-core:^8.7.47- Affected
- >=9.0.0 <9.5.35
- Fixed in
- 9.5.35
composer require typo3/cms-core:^9.5.35- Affected
- >=10.0.0 <10.4.29
- Fixed in
- 10.4.29
composer require typo3/cms-core:^10.4.29- Affected
- >=11.0.0 <11.5.11
- Fixed in
- 11.5.11
composer require typo3/cms-core:^11.5.11- Affected
- >=10.0.0 <10.4.29
- Fixed in
- 10.4.29
composer require typo3/cms:^10.4.29- Affected
- >=11.0.0 <11.5.11
- Fixed in
- 11.5.11
composer require typo3/cms:^11.5.11Details
> ### Meta
> * CVSS: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C (4.9)
Problem
It has been discovered that the Form Designer backend module of the Form Framework is vulnerable to cross-site scripting. A valid backend user account with access to the form module is needed to exploit this vulnerability.
Solution
Update to TYPO3 versions 8.7.47 ELTS, 9.5.35 ELTS, 10.4.29, 11.5.11 that fix the problem described above.
Credits
Thanks to Gabe Troyan who reported and fixed the issue.
References
Is GHSA-3r95-23jp-mhvg 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/security/advisories/GHSA-3r95-23jp-mhvg
- Advisorynvd.nist.gov/vuln/detail/CVE-2022-31048
- Linkgithub.com/TYPO3/typo3/commit/6f2554dc4ea0b670fd5599c54fd788d4db96c4a0
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2022-31048.yaml
- Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2022-31048.yaml
- Packagegithub.com/TYPO3-CMS/core
- Linktypo3.org/security/advisory/typo3-core-sa-2022-003
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.