Privilege Escalation & SQL Injection in TYPO3 CMS
Published 5 Jun 2024 · Updated 2 Dec 2024
Affected packages
- Affected
- >=8.5.0 <8.7.17
- Fixed in
- 8.7.17
composer require typo3/cms:^8.7.17- Affected
- >=9.0.0 <9.3.2
- Fixed in
- 9.3.2
composer require typo3/cms:^9.3.2Details
Failing to properly dissociate system related configuration from user generated configuration, the Form Framework (system extension "form") is vulnerable to SQL injection and Privilege Escalation. Basically instructions can be persisted to a form definition file that were not configured to be modified - this applies to definitions managed using the form editor module as well as direct file upload using the regular file list module. A valid backend user account as well as having system extension form activated are needed in order to exploit this vulnerability.
Is GHSA-7qwg-fcpw-xg5g 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
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.