CVE-2024-25121

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.

ℹ️ 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

• TYPO3-CORE-SA-2024-006

CVE-2024-25121 has a CVSS score of 7.1 (High). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (8.7.57, 9.5.46, 10.4.43, 11.5.35, 12.4.11, 13.0.1); upgrading removes the vulnerable code path.

Kodem intelligence

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.

1. What is CVE-2024-25121? CVE-2024-25121 is a high-severity security vulnerability in typo3/cms-core (composer), affecting versions >= 8.0.0, <= 8.7.56. It is fixed in 8.7.57, 9.5.46, 10.4.43, 11.5.35, 12.4.11, 13.0.1.
2. How severe is CVE-2024-25121? CVE-2024-25121 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of typo3/cms-core are affected by CVE-2024-25121? typo3/cms-core (composer) versions >= 8.0.0, <= 8.7.56 is affected.
4. Is there a fix for CVE-2024-25121? Yes. CVE-2024-25121 is fixed in 8.7.57, 9.5.46, 10.4.43, 11.5.35, 12.4.11, 13.0.1. Upgrade to this version or later.
5. Is CVE-2024-25121 exploitable, and should I be worried? Whether CVE-2024-25121 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2024-25121 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2024-25121?
   • Upgrade typo3/cms-core to 8.7.57 or later
   • Upgrade typo3/cms-core to 9.5.46 or later
   • Upgrade typo3/cms-core to 10.4.43 or later
   • Upgrade typo3/cms-core to 11.5.35 or later
   • Upgrade typo3/cms-core to 12.4.11 or later
   • Upgrade typo3/cms-core to 13.0.1 or later