HighGHSA-rj3x-wvc6-5j66CVE-2024-25121

TYPO3 vulnerable to Improper Access Control Persisting File Abstraction Layer Entities via Data Handler

Published 13 Feb 2024 · Updated 10 Sept 2026

Affected packages

typo3/cms-coreComposer
Affected
>=8.0.0 <8.7.57
Fixed in
8.7.57
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^8.7.57
typo3/cms-coreComposer
Affected
>=9.0.0 <9.5.46
Fixed in
9.5.46
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^9.5.46
typo3/cms-coreComposer
Affected
>=10.0.0 <10.4.43
Fixed in
10.4.43
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^10.4.43
typo3/cms-coreComposer
Affected
>=11.0.0 <11.5.35
Fixed in
11.5.35
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^11.5.35
typo3/cms-coreComposer
Affected
>=12.0.0 <12.4.11
Fixed in
12.4.11
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^12.4.11
typo3/cms-coreComposer
Affected
>=13.0.0 <13.0.1
Fixed in
13.0.1
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^13.0.1

Details

Problem

Entities of the File Abstraction Layer (FAL) could be persisted directly via DataHandler. This allowed attackers to reference files in the fallback storage directly and retrieve their file names and contents. The fallback storage ("zero-storage") is used as a backward compatibility layer for files located outside properly configured file storages and within the public web root directory. Exploiting this vulnerability requires a valid backend user account.

Solution

Update to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described.

ℹ️ Strong security defaults - Manual actions required

When persisting entities of the File Abstraction Layer directly via DataHandler, sys_file entities are now denied by default, and sys_file_reference & sys_file_metadata entities are not permitted to reference files in the fallback storage anymore.

When importing data from secure origins, this must be explicitly enabled in the corresponding DataHandler instance by using $dataHandler->isImporting = true;.

Credits

Thanks to TYPO3 core & security team member Oliver Hader who reported and fixed the issue.

References

Is GHSA-rj3x-wvc6-5j66 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.

Scan a project free, no signupOr connect GitHub to scan every repo

References

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