typo3/cms-core
Affected
- introduced
0, fixed10.4.57(ecosystem)
Fixed versions
10.4.57
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-49738
TYPO3 CMS has Broken Access Control in its File Abstraction Layer
Problem
The path allowance check in GeneralUtility::isAllowedAbsPath() performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like /var/www/html-other/secret.yaml to be incorrectly accepted as valid when the project root was /var/www/html. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check.
Solution
Update to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.
Credits
TYPO3 CMS thanks Wolfgang Klinger for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.
Resources
Low Basis: The source's own band: LOW
0, fixed 10.4.57 (ecosystem)10.4.57
The export has no generic command for this ecosystem.
11.0.0, fixed 11.5.51 (ecosystem)11.5.51
The export has no generic command for this ecosystem.
12.0.0, fixed 12.4.46 (ecosystem)12.4.46
The export has no generic command for this ecosystem.
13.0.0, fixed 13.4.31 (ecosystem)13.4.31
The export has no generic command for this ecosystem.
14.0.0, fixed 14.3.3 (ecosystem)14.3.3
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0