dbcve.org
TYPO3CMS

CVE-2024-25121

HIGH · 7.1 CVSS v3.1 Published 2024-02-13
Fix available
A fix is available. Upgrade to 8.7.57 / 9.5.46 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
TYPO3 is an open source PHP based web content management system released under the GNU GPL. In affected versions of TYPO3 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. Users are advised to update to TYPO3 version 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, or 13.0.1 which fix the problem described. 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;`.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

TYPO3's DataHandler allows direct persistence of File Abstraction Layer (FAL) entities, enabling authenticated backend users to reference files in the fallback storage (zero-storage) used for files outside configured storages but within the web root. This permits unauthorized disclosure of file names and contents.

MitigationUpdate to TYPO3 version 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, or 13.0.1 which enforce restrictions on sys_file entities and prevent fallback storage references.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TYPO3CMS
Affected:>= 8.0.0, < 8.7.57>= 9.0.0, < 9.5.46>= 10.0.0, < 10.4.43>= 11.0.0, < 11.5.35>= 12.0.0, < 12.4.11= 13.0.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed TYPO3 version
    Access the TYPO3 backend, go to Admin Tools > About, or check the composer.json file for the typo3/cms-core version number
    Affected if The installed version is >= 8.0.0 and < 8.7.57, OR >= 9.0.0 and < 9.5.46, OR >= 10.0.0 and < 10.4.43, OR >= 11.0.0 and < 11.5.35, OR >= 12.0.0 and < 12.4.11, OR = 13.0.0
  2. Confirm backend user access exists
    Check if any backend user accounts are created in the TYPO3 installation by querying the be_users database table or checking through the backend user administration module
    Affected if Backend user accounts exist and are active in the system
  3. Verify FAL fallback storage configuration
    Check the sys_file table in the database for records where storage = 0, which indicates the fallback storage is in use. Run: SELECT uid, name, storage FROM sys_file WHERE storage = 0;
    Affected if There are any sys_file records with storage = 0, indicating fallback storage is being used and could be exploited
  4. Check DataHandler accessibility
    Verify that the TYPO3 DataHandler (core processing) is accessible to authenticated backend users through the TYPO3 backend or API endpoints
    Affected if Authenticated backend users have access to create or modify records through DataHandler

Your TYPO3 installation is affected if the installed version falls within the affected ranges AND backend users with write access to FAL entities exist in the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 8.7.57 / 9.5.46 / 10.4.43 or later
Fixed in 8.7.579.5.4610.4.43
Interim mitigation

Update to TYPO3 version 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, or 13.0.1 which enforce restrictions on sys_file entities and prevent fallback storage references.

Recommended fix High confidence

Upgrade to the appropriate fixed version: 8.7.57 (ELTS), 9.5.46 (ELTS), 10.4.43 (ELTS), 11.5.35 (LTS), 12.4.11 (LTS), or 13.0.1 based on your current major branch

  1. Identify the current TYPO3 version from composer.json or typo3/sysext/core/Classes/Information/Typo3Version.php
  2. Backup the database and all files before proceeding with the upgrade
  3. For TYPO3 v8.x: Upgrade to version 8.7.57 (ELTS)
  4. For TYPO3 v9.x: Upgrade to version 9.5.46 (ELTS)
  5. For TYPO3 v10.x: Upgrade to version 10.4.43 (ELTS)
  6. For TYPO3 v11.x: Upgrade to version 11.5.35 (LTS)
  7. For TYPO3 v12.x: Upgrade to version 12.4.11 (LTS)
  8. For TYPO3 v13.x: Upgrade to version 13.0.1
Caveat After upgrading, sys_file entities are denied by default when persisting via DataHandler; if you import data from secure origins, you must explicitly set $dataHandler->isImporting = true; in your code

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in TYPO3 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25121 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-25121 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data