HighGHSA-4rvc-5hrh-qmwfCVE-2010-3662
TYPO3 SQL injection vulnerability on the backend
Published 21 Apr 2022 · Updated 7 Feb 2024
Affected packages
typo3/cms-backendComposer
- Affected
- <4.1.14
- Fixed in
- 4.1.14
Update to the fixed version for your release line, for example:
composer require typo3/cms-backend:^4.1.14typo3/cms-backendComposer
- Affected
- >=4.2.0 <4.2.13
- Fixed in
- 4.2.13
Update to the fixed version for your release line, for example:
composer require typo3/cms-backend:^4.2.13typo3/cms-backendComposer
- Affected
- >=4.3.0 <4.3.4
- Fixed in
- 4.3.4
Update to the fixed version for your release line, for example:
composer require typo3/cms-backend:^4.3.4typo3/cms-backendComposer
- Affected
- >=4.4.0 <4.4.1
- Fixed in
- 4.4.1
Update to the fixed version for your release line, for example:
composer require typo3/cms-backend:^4.4.1Details
TYPO3 before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4 and 4.4.x before 4.4.1 allows SQL Injection on the backend.
Is GHSA-4rvc-5hrh-qmwf 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
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.