MediumGHSA-cvm2-5f78-g9m8CVE-2025-59016
TYPO3 CMS exposes sensitive information in an error message
Published 9 Sept 2025 · Updated 9 Sept 2025
Affected packages
typo3/cms-coreComposer
- 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-core:^12.4.37typo3/cms-coreComposer
- 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-core:^12.4.37typo3/cms-coreComposer
- 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-core:^12.4.37typo3/cms-coreComposer
- 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-core:^12.4.37typo3/cms-coreComposer
- 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-core:^13.4.18Details
Error messages containing sensitive information in the File Abstraction Layer in 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 disclose full file paths via failed low-level file-system operations.
Is GHSA-cvm2-5f78-g9m8 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-core, and gives you the command that fixes it.
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.