Skip to content

← Actionable
High, CVSS 7.2

The TYPO3 CMS Backend has Broken Authentication in Backend MFA

CVE-2025-47941GHSA-744g-7qm9-hjh9

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (typo3/cms-backend 13.4.12, 12.4.31), 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.

Affected packages

  • Packagist typo3/cms-backend

    Affected
    >= 12.0.0, <= 12.4.30>= 13.0.0, <= 13.4.11
    Fixed in
    13.4.12, 12.4.31

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.2 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2025-47941: 0.47% estimated exploitation activity in the next 30 days; percentile 40.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 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. Solution Update to TYPO3 versions 12.4.31 LTS, 13.4.12 LTS that fix the problem described. Credits Thanks to Jens Jacobsen and Y. Kahveci for reporting this issue, and to TYPO3 security team member Torben Hansen for fixing it.

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

    Published from ghsa record GHSA-744g-7qm9-hjh9

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-2025-47941

Advisory: The TYPO3 CMS Backend has Broken Authentication in Backend MFA
IDs: CVE-2025-47941, GHSA-744g-7qm9-hjh9
Record: https://patchnext.com/advisories/cve-2025-47941 (revision 1, source checked 26 Oct 2026, 14:33 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms-backend 13.4.12, 12.4.31. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms-backend: affected >= 12.0.0, <= 12.4.30; >= 13.0.0, <= 13.4.11; fixed in 13.4.12, 12.4.31

## Suggested inspection (read-only)
- Packagist typo3/cms-backend: 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-backend.
- 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-744g-7qm9-hjh9 (GitHub-reviewed advisory GHSA-744g-7qm9-hjh9 lists affected ranges: Packagist typo3/cms-backend >=12.0.0 =13.0.0 <=13.4.11)

Commands are suggestions: review each one before running it.

Loading voting…