dbcve.org
TYPO3CMS

CVE-2025-59020

MEDIUM · 6.5 CVSS v3.1 Published 2026-01-13
Fix available
A fix is available. Upgrade to 10.4.55 / 11.5.49 or later.
See remediation →
71/100
Remediation priority · Elevated
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
By exploiting the defVals parameter, attackers could bypass field‑level access checks during record creation in the TYPO3 backend. This gave them the ability to insert arbitrary data into prohibited exclude fields of a database table for which the user already has write permission for a reduced set of fields. This issue affects TYPO3 CMS versions 10.0.0-10.4.54, 11.0.0-11.5.48, 12.0.0-12.4.40, 13.0.0-13.4.22 and 14.0.0-14.0.1.

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-863

An authorization check exists but is flawed, so it passes when it should fail. Attackers probe roles and object references to find the gap. Remediation means centralising and correctly implementing the access-control logic, then testing it against every role.

General guidance for the incorrect 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 →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TYPO3CMS
Affected:>= 10.0.0, < 10.4.55>= 11.0.0, < 11.5.49>= 12.0.0, < 12.4.41>= 13.0.0, < 13.4.23>= 14.0.0, < 14.0.2

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
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

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
Upgrade available Upgrade to 10.4.55 / 11.5.49 / 12.4.41 or later
Fixed in 10.4.5511.5.4912.4.41
Vendor patch github.com →
Recommended fix High confidence

Upgrade to the latest patch release in your current major version branch: 10.4.55 (for 10.x), 11.5.49 (for 11.x), 12.4.41 (for 12.x), or 13.4.23 (for 13.x)

  1. 1. Identify the currently installed TYPO3 version by checking the composer.json or the TYPO3 backend About module
  2. 2. Determine which version branch you are on (10.x, 11.x, 12.x, or 13.x)
  3. 3. For TYPO3 10.x: Upgrade to version 10.4.55 or later
  4. 4. For TYPO3 11.x: Upgrade to version 11.5.49 or later
  5. 5. For TYPO3 12.x: Upgrade to version 12.4.41 or later
  6. 6. For TYPO3 13.x: Upgrade to version 13.4.23 or later
  7. 7. Clear all caches after the upgrade (via Install Tool or CLI: typo3cms cache:flush)
  8. 8. Verify the fix by testing record creation in the backend with users that have restricted field permissions
Caveat TYPO3 minor/patch upgrades typically have low breaking change risk, but always review the release notes for any deprecation notices or configuration changes before upgrading

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59020 — 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-2025-59020 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