Skip to main content
VulnerabilityPublished Updated

CVE-2026-11607: TYPO3 CMS · Missing Authorization

Affects TYPO3 CMSSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 7.6 High · fixed in 14.3.3 : patch TYPO3 CMS soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 4.0 base score
7.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 14.3.3, 13.4.31, 12.4.46 +6
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

ProductAffectedFixed in
TYPO3TYPO3 CMSAffected
  • >=14.0.0 <14.3.3
Fixed in
  • 14.3.3
TYPO3TYPO3 CMSAffected
  • >=13.0.0 <13.4.31
Fixed in
  • 13.4.31
TYPO3TYPO3 CMSAffected
  • >=12.0.0 <12.4.46
Fixed in
  • 12.4.46
TYPO3TYPO3 CMSAffected
  • >=11.0.0 <11.5.51
Fixed in
  • 11.5.51
TYPO3TYPO3 CMSAffected
  • <10.4.57
Fixed in
  • 10.4.57
GitHubtypo3/typo3pkg:github/typo3/typo3Other threatsAffected
  • <10.4.57
  • 11.0.0 <11.5.52
  • 12.0.0 <12.4.47
  • 13.0.0 <13.4.32
  • 14.0.0 <14.3.4
Fixed in
  • 10.4.57
  • 11.5.52
  • 12.4.47
  • 13.4.32
  • 14.3.4

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

If you cannot patch yet, restrict backend user access to trusted personnel only and monitor for suspicious activity related to form definitions. Follow vendor advisories closely for updates on remediation.

Description

Backend users with access to the Form Framework were able to use files not ending in .form.yaml as form definitions, which were processed without denying the incorrect file extension. Maliciously crafted form definition files can be used to execute arbitrary SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.

References

Community reviews

Loading reviews…