CriticalGHSA-gwfx-p7mr-f92v

Missing Access Check in TYPO3 CMS

Published 5 Jun 2024 · Updated 2 Dec 2024

Affected packages

typo3/cmsComposer
Affected
>=6.2.0 <6.2.25
Fixed in
6.2.25
Update to the fixed version for your release line, for example:composer require typo3/cms:^6.2.25
typo3/cmsComposer
Affected
>=7.6.0 <7.6.8
Fixed in
7.6.8
Update to the fixed version for your release line, for example:composer require typo3/cms:^7.6.8
typo3/cmsComposer
Affected
>=8.0.0 <8.1.1
Fixed in
8.1.1
Update to the fixed version for your release line, for example:composer require typo3/cms:^8.1.1

Details

Extbase request handling fails to implement a proper access check for requested controller/ action combinations, which makes it possible for an attacker to execute arbitrary Extbase actions by crafting a special request. To successfully exploit this vulnerability, an attacker must have access to at least one Extbase plugin or module action in a TYPO3 installation. The missing access check inevitably leads to information disclosure or remote code execution, depending on the action that an attacker is able to execute.

Is GHSA-gwfx-p7mr-f92v 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.