MediumGHSA-947m-vgqc-x6v4CVE-2012-6144
Typo3 Backend History Module Vulnerable to SQL Injection
Published 17 May 2022 · Updated 12 Jan 2024
Affected packages
typo3/cmsComposer
- Affected
- >=4.5.0 <4.5.21
- Fixed in
- 4.5.21
Update to the fixed version for your release line, for example:
composer require typo3/cms:^4.5.21typo3/cmsComposer
- Affected
- >=4.6.0 <4.6.14
- Fixed in
- 4.6.14
Update to the fixed version for your release line, for example:
composer require typo3/cms:^4.6.14typo3/cmsComposer
- Affected
- >=4.7.0 <4.7.6
- Fixed in
- 4.7.6
Update to the fixed version for your release line, for example:
composer require typo3/cms:^4.7.6Details
SQL injection vulnerability in the Backend History module in TYPO3 4.5.x before 4.5.21, 4.6.x before 4.6.14, and 4.7.x before 4.7.6 Due to missing encoding of user input, the history module is susceptible to SQL Injection and Cross-Site Scripting. A valid backend login is required to exploit this vulnerability.
Is GHSA-947m-vgqc-x6v4 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.