dbcve.org
TYPO3CMS

CVE-2025-47941

HIGH · 7.2 CVSS v3.1 Published 2025-05-20
Fix available
A fix is available. Upgrade to 12.4.31 / 13.4.12 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. In versions on the 12.x branch prior to 12.4.31 LTS and the 13.x branch prior to 13.4.2 LTS, the multifactor authentication (MFA) dialog presented during backend login can be bypassed due to insufficient enforcement of access restrictions on all backend routes. Successful exploitation requires valid backend user credentials, as MFA can only be bypassed after successful authentication. Users should update to TYPO3 version 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's multifactor authentication (MFA) mechanism can be bypassed due to insufficient access restrictions on backend routes. After valid credentials are submitted, the MFA dialog fails to properly enforce protection on all backend routes, allowing authenticated users to potentially access the system without completing MFA. This is a logic/bypass vulnerability rather than a direct authentication bypass.

MitigationUpdate TYPO3 to version 12.4.31 LTS or 13.4.2 LTS to patch the MFA enforcement flaw. After updating, verify that MFA is properly enforced across all backend routes.

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:>= 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
    Locate the TYPO3 version by checking the composer.json file or the VERSION file in theTYPO3 root directory, or query the TYPO3 system information via the backend admin tool.
    Affected if The installed version is 12.0.0 through 12.4.30, or 13.0.0 through 13.4.11 (falls within >=12.0.0,<12.4.31 or >=13.0.0,<13.4.12).
  2. Verify MFA is configured
    In the TYPO3 backend, navigate to User Settings > Enable Multi-Factor Authentication, or check the sys_registry database table for mfa_provider records.
    Affected if MFA is enabled for at least one backend user account.
  3. Inspect backend route protection
    Examine the TYPO3 routing configuration for backend routes in the sitepackage or custom extensions, specifically checking for missing requireMFA attributes on route definitions.
    Affected if Backend routes exist that lack proper MFA enforcement flags or requireMMA configuration.
  4. Test route access after credentials but before MFA completion
    Log in with valid credentials to trigger the MFA prompt, then attempt to directly access backend routes (such as /typo3/module/system/infopage or other admin routes) by constructing the URL directly without completing MFA.
    Affected if Any backend route becomes accessible without completing the MFA challenge after initial login.

You are affected if your TYPO3 installation version falls within the vulnerable range AND MFA is enabled, allowing unauthorized backend access without completing MFA verification.

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 12.4.31 / 13.4.12 or later
Fixed in 12.4.3113.4.12
Interim mitigation

Update TYPO3 to version 12.4.31 LTS or 13.4.2 LTS to patch the MFA enforcement flaw. After updating, verify that MFA is properly enforced across all backend routes.

Recommended fix High confidence

TYPO3 12.4.31 LTS (for 12.x installations) or TYPO3 13.4.12 LTS (for 13.x installations)

  1. 1. Back up the TYPO3 database and entire file system before proceeding
  2. 2. If using Composer, run: composer require typo3/cms-core:^12.4.31 or composer require typo3/cms-core:^13.4.12 depending on your branch
  3. 3. If not using Composer, download the appropriate version from typo3.org/download and follow the upgrade documentation
  4. 4. Clear all caches: rm -rf var/cache/* var/generated/*
  5. 5. Log in to the backend and verify the MFA dialog is properly enforced
  6. 6. Test that MFA authentication works correctly for backend users
Caveat Patch releases within the same minor version (e.g., 12.4.x to 12.4.31) typically contain no breaking changes; however, if migrating from 12.x to 13.x, review the TYPO3 v13 migration guide for breaking changes

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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