dbcve.org
TYPO3CMS

CVE-2025-47940

HIGH · 7.2 CVSS v3.1 Published 2025-05-20
Fix available
A fix is available. Upgrade to 10.4.50 / 11.5.44 or later.
See remediation →
78/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. Starting in version 10.0.0 and prior to versions 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, and 13.4.12 LTS, administrator-level backend users without system maintainer privileges can escalate their privileges and gain system maintainer access. Exploiting this vulnerability requires a valid administrator account. Users should update to TYPO3 version 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, or 13.4.12 LTS to fix the problem.

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 CMS contains a privilege escalation vulnerability where authenticated administrator-level backend users can elevate their privileges to system maintainer access. This bypasses the authorization check that should separate administrator privileges from system maintainer privileges.

MitigationUpdate TYPO3 to version 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, or 13.4.12 LTS. Until patched, audit admin accounts and monitor for unauthorized system maintainer access.

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:>= 10.4.0, < 10.4.50>= 11.0.0, < 11.5.44>= 12.0.0, < 12.4.31>= 13.0.0, < 13.4.12

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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
    Open the file or use the command line to read the VERSION file in the TYPO3 root directory, or access the TYPO3 install tool and check the version information
    Affected if The installed version falls within the ranges: 10.4.0 to 10.4.49, 11.0.0 to 11.5.43, 12.0.0 to 12.4.30, or 13.0.0 to 13.4.11
  2. Identify administrator-level backend users
    In the TYPO3 backend, navigate to the User Management module and filter for users with the 'admin' flag enabled, or query the be_users table in the database for records where the 'admin' field equals 1
    Affected if Any active user account with administrator privileges exists in the system
  3. Review system maintainer accounts
    Access the TYPO3 backend User Management module and examine the system maintainer list, or query the sys_registry table for entries in the 'systemMaintainers' key
    Affected if There are system maintainer accounts present, especially any that were not explicitly created by existing legitimate maintainers
  4. Compare admin to maintainer role assignments
    Cross-reference the list of admin users against the list of system maintainers to identify any accounts that have both administrator privileges AND system maintainer status, or query the be_users and sys_registry tables to compare user UIDs
    Affected if Any user account has both administrator-level backend access AND system maintainer privileges assigned simultaneously

You are affected if your TYPO3 version is within the vulnerable ranges AND you have administrator-level backend users present, as the vulnerability allows such admins to escalate to system maintainer access.

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 10.4.50 / 11.5.44 / 12.4.31 or later
Fixed in 10.4.5011.5.4412.4.31
Interim mitigation

Update TYPO3 to version 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, or 13.4.12 LTS. Until patched, audit admin accounts and monitor for unauthorized system maintainer access.

Recommended fix High confidence

Upgrade to TYPO3 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, or 13.4.12 LTS (choose the appropriate branch)

  1. 1. Create a complete backup of the TYPO3 database and all files
  2. 2. Review installed extensions for compatibility with the target TYPO3 version
  3. 3. Update TYPO3 core to version 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, or 13.4.12 LTS depending on your current branch (for 10.4.x upgrade to 10.4.50, for 11.x upgrade to 11.5.44, for 12.x upgrade to 12.4.31, for 13.x upgrade to 13.4.12)
  4. 4. Run database migration scripts if any are required
  5. 5. Clear all TYPO3 caches (via Install Tool or command line)
  6. 6. Verify administrator privileges are correctly scoped and test that non-maintainer admin accounts cannot access system maintainer functions
Caveat Standard TYPO3 upgrade considerations apply - review deprecation warnings, ensure extensions are compatible, and test thoroughly in a staging environment before production deployment

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

Fix this in TYPO3 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47940 — 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-2025-47940 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