MediumGHSA-2fhw-2j7m-mr4mCVE-2025-59017

TYPO3 backend modules have Broken Access Control

Published 9 Sept 2025 · Updated 9 Sept 2025

Affected packages

Affected
>=9.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-workspaces:^12.4.37
Affected
>=10.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-workspaces:^12.4.37
Affected
>=11.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-workspaces:^12.4.37
Affected
>=12.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-workspaces:^12.4.37
Affected
>=13.0.0 <13.4.18
Fixed in
13.4.18
Update to the fixed version for your release line, for example:composer require typo3/cms-workspaces:^13.4.18
Affected
>=9.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-recycler:^12.4.37
Affected
>=10.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-recycler:^12.4.37
Affected
>=11.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-recycler:^12.4.37
Affected
>=12.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-recycler:^12.4.37
Affected
>=13.0.0 <13.4.18
Fixed in
13.4.18
Update to the fixed version for your release line, for example:composer require typo3/cms-recycler:^13.4.18
Affected
>=10.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-dashboard:^12.4.37
Affected
>=11.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-dashboard:^12.4.37
Affected
>=12.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-dashboard:^12.4.37
Affected
>=13.0.0 <13.4.18
Fixed in
13.4.18
Update to the fixed version for your release line, for example:composer require typo3/cms-dashboard:^13.4.18
Affected
>=13.0.0 <13.4.18
Fixed in
13.4.18
Update to the fixed version for your release line, for example:composer require typo3/cms-beuser:^13.4.18
Affected
>=12.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-beuser:^12.4.37
Affected
>=11.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-beuser:^12.4.37
Affected
>=10.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-beuser:^12.4.37
Affected
>=9.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-beuser:^12.4.37
Affected
>=9.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-backend:^12.4.37
Affected
>=10.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-backend:^12.4.37
Affected
>=11.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-backend:^12.4.37
Affected
>=12.0.0 <12.4.37
Fixed in
12.4.37
Update to the fixed version for your release line, for example:composer require typo3/cms-backend:^12.4.37
Affected
>=13.0.0 <13.4.18
Fixed in
13.4.18
Update to the fixed version for your release line, for example:composer require typo3/cms-backend:^13.4.18

Details

Missing authorization checks in the Backend Routing of TYPO3 CMS versions 9.0.0‑9.5.54, 10.0.0‑10.4.53, 11.0.0‑11.5.47, 12.0.0‑12.4.36, and 13.0.0‑13.4.17 allow backend users to directly invoke AJAX backend routes without having access to the corresponding backend modules.

Is GHSA-2fhw-2j7m-mr4m 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-workspaces, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.