Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.1

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

CVE-2024-25121GHSA-rj3x-wvc6-5j66

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (typo3/cms-core 13.0.1, 12.4.11, 11.5.35, 10.4.43, 9.5.46, 8.7.57), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist typo3/cms-core

    Affected
    >= 8.0.0, <= 8.7.56>= 9.0.0, <= 9.5.45>= 10.0.0, <= 10.4.42>= 11.0.0, <= 11.5.34>= 12.0.0, <= 12.4.10>= 13.0.0, <= 13.0.0
    Fixed in
    8.7.57, 12.4.11, 9.5.46, 10.4.43, 11.5.35, 13.0.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
EPSS
  • CVE-2024-25121: 0.50% estimated exploitation activity in the next 30 days; percentile 42.63 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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, sysfile entities are now denied by default, and sysfilereference & sysfilemetadata 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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-rj3x-wvc6-5j66

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-25121

Advisory: TYPO3 vulnerable to Improper Access Control Persisting File Abstraction Layer Entities via Data Handler
IDs: CVE-2024-25121, GHSA-rj3x-wvc6-5j66
Record: https://patchnext.com/advisories/cve-2024-25121 (revision 1, source checked 26 Oct 2026, 14:18 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms-core 13.0.1, 12.4.11, 11.5.35, 10.4.43, 9.5.46, 8.7.57. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms-core: affected >= 8.0.0, <= 8.7.56; >= 9.0.0, <= 9.5.45; >= 10.0.0, <= 10.4.42; >= 11.0.0, <= 11.5.34; >= 12.0.0, <= 12.4.10; >= 13.0.0, <= 13.0.0; fixed in 8.7.57, 12.4.11, 9.5.46, 10.4.43, 11.5.35, 13.0.1

## Suggested inspection (read-only)
- Packagist typo3/cms-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typo3/cms-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-rj3x-wvc6-5j66 (GitHub-reviewed advisory GHSA-rj3x-wvc6-5j66 lists affected ranges: Packagist typo3/cms-core >=8.0.0 =9.0.0 =10.0.0 =11.0.0 =12.0.0 =13.0.0 <=13.0.0)

Commands are suggestions: review each one before running it.

Loading voting…