Is CVE-2026-11607 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-11607 being exploited in the wild.

How severe is CVE-2026-11607?

High severity, with a CVSS score of 4, published 9 June 2026.

Which products and versions are affected?

typo3/cms-core (Packagist) ECOSYSTEM:introduced=0,fixed=10.4.57; typo3/cms-form (Packagist) ECOSYSTEM:introduced=0,fixed=10.4.57.

Is there a fix for CVE-2026-11607?

Yes. typo3/cms-core (Packagist): upgrade to 10.4.57 or later; typo3/cms-form (Packagist): upgrade to 10.4.57 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-11607 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-11607?

Check whether you run typo3/cms-core (Packagist) or typo3/cms-form (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-11607: TYPO3 CMS privilege escalation in Form Framework

CVE-2026-11607 · Severity: high · CVSS 4 · Published 2026-06-09

TYPO3 CMS, a popular enterprise content management system, contains a security flaw in its form-building tool. This vulnerability allows users who already have limited access to the backend to bypass file restrictions and execute malicious database commands. An attacker could use this to take full control of the website by creating new administrator accounts.

Technologies: typo3/cms-core (Packagist), typo3/cms-form (Packagist). Vendors: Packagist.

Quick answers

Is CVE-2026-11607 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-11607 being exploited in the wild.
How severe is CVE-2026-11607?: High severity, with a CVSS score of 4, published 9 June 2026.
Which products and versions are affected?: typo3/cms-core (Packagist) ECOSYSTEM:introduced=0,fixed=10.4.57; typo3/cms-form (Packagist) ECOSYSTEM:introduced=0,fixed=10.4.57.
Is there a fix for CVE-2026-11607?: Yes. typo3/cms-core (Packagist): upgrade to 10.4.57 or later; typo3/cms-form (Packagist): upgrade to 10.4.57 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-11607 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-11607?: Check whether you run typo3/cms-core (Packagist) or typo3/cms-form (Packagist) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

typo3/cms-core (Packagist): upgrade to 10.4.57 or later
```
composer require typo3/cms-core:^10.4.57
```
typo3/cms-form (Packagist): upgrade to 10.4.57 or later
```
composer require typo3/cms-form:^10.4.57
```

Technical details

A missing authorization and improper file extension validation vulnerability exists in the TYPO3 Form Framework (CWE-862). Backend users with access to the framework can provide form definition files that do not use the mandatory '.form.yaml' extension. These maliciously crafted files are processed by the system, leading to the execution of arbitrary SQL statements. An attacker with low-level backend privileges can exploit this to perform unauthorized database operations, such as creating new administrative user accounts. The issue is resolved in TYPO3 versions 10.4.57 ELTS, 11.5.51 ELTS, 12.4.46 ELTS, 13.4.31 LTS, and 14.3.3 LTS.

Affected products

TYPO3 TYPO3 CMS < 10.4.57, 11.0.0 < 11.5.51, 12.0.0 < 12.4.46, 13.0.0 < 13.4.31, 14.0.0 < 14.3.3

Identifiers

CVE-2026-11607
GHSA-pjpj-v387-x4vq

Timeline

2026-06-09: disclosed
2026-06-09: patched
2026-06-12: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.