dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-11607

HIGH · 7.6 CVSS v4.0 Published 2026-06-09
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
82/100
Remediation priority · High
Remotely reachable Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-862

The application checks who you are but not whether you're allowed to perform a given action, so any authenticated user can reach things meant for others. This is the classic “change the ID in the URL” bug. The fix is an authorization check on every request, evaluated against the acting user's permissions.

General guidance for the missing authorization class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Recommended fix High confidence

Upgrade to TYPO3 CMS 10.4.57 / 11.5.51 / 12.4.46 / 13.4.31 / 14.3.3 or later depending on your current major version

  1. 1. Identify the currently installed TYPO3 CMS version by checking the composer.json file or the TYPO3 backend (Admin Tools > About).
  2. 2. Based on the identified version, determine the target upgrade version: for 10.x upgrade to 10.4.57+, for 11.x upgrade to 11.5.51+, for 12.x upgrade to 12.4.46+, for 13.x upgrade to 13.4.31+, for 14.x upgrade to 14.3.3+.
  3. 3. Create a complete backup of the database and all files, including composer.json and composer.lock.
  4. 4. Update composer.json to require the target patch version: for example, change "typo3/cms":"^12.4" to "typo3/cms":"^12.4.46".
  5. 5. Run `composer update typo3/cms` to fetch and install the patched version.
  6. 6. Verify the upgrade by checking the TYPO3 backend version (Admin Tools > About).
  7. 7. Clear all caches via the Install Tool or by deleting var/cache/* and var/tmp/* directories.
  8. 8. Test the Form Framework functionality to ensure the file extension validation is working correctly.
Caveat Major version upgrades (e.g., 12.x to 13.x) may have breaking changes; review the release notes for deprecations and migration requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can apply and verify the patch for your build — typical engagement from $1,950. Get the patch applied

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11607 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11607 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data