TYPO3 Allows Information Disclosure via DBAL Restriction Handling
Published 20 May 2025 · Updated 20 May 2025
Affected packages
- Affected
- >=9.0.0 <9.5.51
- Fixed in
- 9.5.51
composer require typo3/cms-core:^9.5.51- Affected
- >=10.0.0 <10.4.50
- Fixed in
- 10.4.50
composer require typo3/cms-core:^10.4.50- Affected
- >=11.0.0 <11.5.44
- Fixed in
- 11.5.44
composer require typo3/cms-core:^11.5.44- Affected
- >=12.0.0 <12.4.31
- Fixed in
- 12.4.31
composer require typo3/cms-core:^12.4.31- Affected
- >=13.0.0 <13.4.12
- Fixed in
- 13.4.12
composer require typo3/cms-core:^13.4.12Details
Problem
When performing a database query involving multiple tables through the database abstraction layer (DBAL), frontend user permissions are only applied via FrontendGroupRestriction to the last table. As a result, data from additional tables included in the same query may be unintentionally exposed to unauthorized users.
Solution
Update to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.
Credits
Thanks to Christian Futterlieb for reporting this issue, and to TYPO3 security team member Elias Häußler for fixing it.
Is GHSA-x8pv-fgxp-8v3x 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.