MediumGHSA-v5jp-4h2p-j2p4
Privilege Escalation in TYPO3 CMS
Published 5 Jun 2024 · Updated 2 Dec 2024
Affected packages
typo3/cmsComposer
- Affected
- >=6.2.0 <6.2.20
- Fixed in
- 6.2.20
Update to the fixed version for your release line, for example:
composer require typo3/cms:^6.2.20typo3/cmsComposer
- Affected
- >=7.6.0 <7.6.5
- Fixed in
- 7.6.5
Update to the fixed version for your release line, for example:
composer require typo3/cms:^7.6.5typo3/cmsComposer
- Affected
- >=8.0.0 <8.0.1
- Fixed in
- 8.0.1
Update to the fixed version for your release line, for example:
composer require typo3/cms:^8.0.1Details
The workspace/ version preview link created by a privileged (backend) user could be abused to obtain certain editing permission, if the admin panel is configured to be shown. A valid preview link is required to exploit this vulnerability.
Is GHSA-v5jp-4h2p-j2p4 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.