Vulnerability advisory

GHSA-3jrg-97f3-rqh9

TYPO3 Unverified Password Change for Backend Users

Published Updated OSV record ↗

Also known as CVE-2025-47938

Severity
  • CVSS 3.xCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N

Affected versions

AffectedFixed in
10.0.0 to before 10.4.5010.4.50Advisories →
Also listed as affected (43)
11.0.0 to before 11.5.4411.5.44Advisories →
Also listed as affected (51)
12.0.0 to before 12.4.3112.4.31Advisories →
Also listed as affected (38)
13.0.0 to before 13.4.1213.4.12Advisories →
Also listed as affected (20)
AffectedFixed in
10.0.0 to before 10.4.5010.4.50Advisories →
Also listed as affected (43)
11.0.0 to before 11.5.4411.5.44Advisories →
Also listed as affected (51)
12.0.0 to before 12.4.3112.4.31Advisories →
Also listed as affected (38)
13.0.0 to before 13.4.1213.4.12Advisories →
Also listed as affected (19)

Description

Problem

The backend user management interface allows password changes without requiring the current password. When an administrator updates their own account or modifies other user accounts via the admin interface, the current password is not requested for verification.

This behavior may lower the protection against unauthorized access in scenarios where an admin session is hijacked or left unattended, as it enables password changes without additional authentication.

Solution

Update to TYPO3 versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, 13.4.12 LTS that fix the problem described.

[!NOTE] In these versions, administrators are required to verify their identity through step-up authentication (also known as sudo mode) when changing backend user passwords.

Credits

Thanks to the National Cyber Security Center (NCSC) of Switzerland for reporting this issue, and to TYPO3 core & security team member Benjamin Franzke for fixing it.

References

  • Codex
  • Claude Code
  • VS Code
  • GitHub Copilot
  • Cursor
  • Cline
  • Windsurf
  • Google Anti-gravity
  • OpenCode
  • Pi
  • Gemini CLI
  • Hermes Agent
  • Zed
  • Junie
  • Qwen Code
  • Kiro
  • Kilo Code
  • Factory Droid

Set up GitHits for your agents

Run this command:

<> bash
npx githits@latest init

What happens next:

  1. Opens your browser to authorize GitHits
  2. Asks whether to set up GitHits at the user or project level
  3. Detects your supported AI coding tools
  4. Lets you choose which tools to configure
  5. Configures the selected tools