Skip to content
Noroxi
NVD / CVE Program· CNA TYPO3

CVE-2025-59020: TYPO3 CMS Allows Broken Access Control in Edit Document Controller

Noroxi assessment

Priority: Monitor (action score 21/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.31% (FIRST EPSS).
  • Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
  • Fixed version: TYPO3 TYPO3 CMS 10.4.55, 11.5.49, 12.4.41.

Low priority for now. Upgrade to TYPO3 TYPO3 CMS 10.4.55, 11.5.49, 12.4.41 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

MediumCVSS 5.3 · v4.0—No exploit Fix available
Published
Jan 13, 2026
Updated
Jun 17, 2026
EPSS
0.3% · 24th percentile

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
21 / 40 · 5.3 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.3%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · TYPO3
5.3
NVD has not scored this yet; the score shown is the CNA’s.

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-59020

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for typo3 records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
typo3typo3

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • typo3 typo310.0.0 and later · before 10.4.55
  • typo3 typo311.0.0 and later · before 11.5.49
  • typo3 typo312.0.0 and later · before 12.4.41
  • typo3 typo313.0.0 and later · before 13.4.23
  • typo3 typo314.0.0 and later · before 14.0.2

Versions reported by the vendor

Affected version ranges reported by the assigning authority (TYPO3). Independent of NVD's CPE analysis and usually ahead of it.

  • TYPO3 TYPO3 CMS

    • 10.0.0 and later · before 10.4.55affected · semver
    • 11.0.0 and later · before 11.5.49affected · semver
    • 12.0.0 and later · before 12.4.41affected · semver
    • 13.0.0 and later · before 13.4.23affected · semver
    • 14.0.0 and later · before 14.0.2affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Packagisttypo3/cms-backendfrom 10.0.0 · before 10.4.5510.4.55
Packagisttypo3/cms-backendfrom 11.0.0 · before 11.5.4911.5.49
Packagisttypo3/cms-backendfrom 12.0.0 · before 12.4.4112.4.41
Packagisttypo3/cms-backendfrom 13.0.0 · before 13.4.2313.4.23
Packagisttypo3/cms-backendfrom 14.0.0 · before 14.0.214.0.2

Same product

typo3: all records

Other highest-scoring records for the same primary product.

  • CVE-2009-0255The System extension Install tool in TYPO3 4.0.0 through 4.0.9, 4.1.0 through 4.1.7, and 4.2.0 through 4.2.3 creates the encryption key with
    60This week
  • CVE-2013-6288Unspecified vulnerability in the Apache Solr for TYPO3 (solr) extension before 2.8.3 for TYPO3 has unknown impact and remote attack vectors,
    41Plan
  • CVE-2013-5303Unspecified vulnerability in the Store Locator (locator) extension before 3.1.5 for TYPO3 has unknown impact and remote attack vectors, rela
    41Plan

Published before and after this one in the same product

  • ← EarlierCVE-2025-59018Sep 9, 2025 · Information Disclosure in Workspaces Module
    28Monitor
  • ← EarlierCVE-2025-59019Sep 9, 2025 · Information Disclosure via CSV Download
    21Monitor
  • Later →CVE-2025-59021Jan 13, 2026 · TYPO3 CMS Allows Broken Access Control in Redirects Module
    21Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
TYPO3 TYPO3 CMS10.4.55Vendor (CNA)
TYPO3 TYPO3 CMS11.5.49Vendor (CNA)
TYPO3 TYPO3 CMS12.4.41Vendor (CNA)
TYPO3 TYPO3 CMS13.4.23Vendor (CNA)
TYPO3 TYPO3 CMS14.0.2Vendor (CNA)
Packagist:typo3/cms-backend10.4.55Package registry (OSV)
Packagist:typo3/cms-backend11.5.49Package registry (OSV)
Packagist:typo3/cms-backend12.4.41Package registry (OSV)
Packagist:typo3/cms-backend13.4.23Package registry (OSV)
Packagist:typo3/cms-backend14.0.2Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2025-47937238 days apartTYPO3 Vulnerable to Information Disclosure via DBAL Restriction Handling
    21Monitor
  • CVE-2024-47780462 days apartInformation Disclosure in TYPO3 Page Tree
    17Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • A low-privileged account is enough.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability
Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
X

Weakness class (CWE)

CWE-863 · Incorrect Authorization

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/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

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records