Vulnerability advisory

GHSA-hwvq-2w67-rvxp

TYPO3 CMS has Broken Access Control in its Form Framework

Published Updated OSV record ↗

Also known as CVE-2026-47346

Severity
  • CVSS 4.0CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Affected versions

AffectedFixed in
All versions before 10.4.5710.4.57Advisories →
Also listed as affected (110)
11.0.0 to before 11.5.5111.5.51Advisories →
Also listed as affected (51)
12.0.0 to before 12.4.4612.4.46Advisories →
Also listed as affected (53)
13.0.0 to before 13.4.3113.4.31Advisories →
Also listed as affected (39)
14.0.0 to before 14.3.314.3.3Advisories →
Also listed as affected (9)
AffectedFixed in
All versions before 10.4.5710.4.57Advisories →
Also listed as affected (110)
11.0.0 to before 11.5.5111.5.51Advisories →
Also listed as affected (51)
12.0.0 to before 12.4.4612.4.46Advisories →
Also listed as affected (53)
13.0.0 to before 13.4.3113.4.31Advisories →
Also listed as affected (38)
14.0.0 to before 14.3.314.3.3Advisories →
Also listed as affected (9)

Description

Problem

Backend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., .FORM.YAML) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts.

Solution

Update to TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, 14.3.3 LTS that fix the problem described.

Credits

TYPO3 CMS thanks Alexander Künzl for reporting this issue, and to TYPO3 core & security team members Oliver Hader and Benjamin Franzke for fixing it.

Resources

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