CVE-2025-59020VulnerabilityPublished 13 Jan 2026

CVE-2025-59020: TYPO3 CMS · Incorrect Authorization

Affects TYPO3 CMSSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · fixed in 14.0.2 : update TYPO3 CMS when convenient.

Data as of 26 Oct 2026, 08:30 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 14.0.2, 13.4.23, 12.4.41 +2

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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade to a fixed release listed under Affected software.

Affected software

Product	Affected	Fixed in
TYPO3TYPO3 CMS	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	Fixed in 14.0.2 13.4.23 12.4.41 11.5.49 10.4.55
Packagisttypo3/cms`pkg:composer/typo3/cms`Other threats	Affected 10.0.0 <=10.4.54 11.0.0 <=11.5.48 12.0.0 <=12.4.40 13.0.0 <=13.4.22 14.0.0 <=14.0.1 =10.0.0 =11.0.0 =12.0.0 =13.0.0 =14.0.0	Fixed in–
Packagisttypo3/cms-backend`pkg:composer/typo3/cms-backend`Other threats	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	Fixed in 10.4.55 11.5.49 12.4.41 13.4.23 14.0.2

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

AI-suggested

1. Immediately review and restrict write permissions in TYPO3 backend to the minimum necessary, ensuring users cannot write to sensitive or exclude fields. 2. 3. Implement strict input validation and sanitization on the defVals parameter if custom extensions or integrations handle it. 4. Conduct thorough audits of backend user roles and permissions to detect and remediate any over-privileged accounts. 5. Monitor TYPO3 CMS logs for unusual record creation activities or attempts to manipulate exclude fields. 6. Consider deploying Web Application Firewalls (WAF) with custom rules to detect and block suspicious defVals parameter usage. 7. Educate administrators and developers about the risks of field-level access bypass and enforce secure coding practices. 8. For critical environments, isolate TYPO3 backend access to trusted networks or VPNs to reduce exposure. 9. Regularly back up TYPO3 databases and content to enable recovery from unauthorized changes. 10. Engage with TYPO3 community and security advisories to stay informed about patches and exploit developments.

Description

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.

Impact

For European organizations, this vulnerability poses a risk of unauthorized data manipulation within TYPO3 CMS-managed websites or applications. Attackers with limited write access could inject arbitrary data into restricted fields, potentially leading to data integrity issues, unauthorized content changes, or exposure of sensitive information stored in exclude fields. This could undermine trust in web services, damage organizational reputation, and lead to compliance violations under regulations such as GDPR if personal or sensitive data is affected. Since TYPO3 is widely used by public sector entities, educational institutions, and enterprises across Europe, exploitation could disrupt critical web services or lead to data leakage. The medium severity score indicates moderate risk, but the broad version range affected and the common use of TYPO3 in Europe elevate the threat. The absence of known exploits reduces immediate risk but does not preclude future attacks. Organizations with multi-tenant or role-based access control configurations in TYPO3 are particularly vulnerable if write permissions are not tightly controlled.

CWE-863Incorrect Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #17OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 13 Jan 2026, 12:26 UTC

WeaknessesCWE-863

Technical details

References

Community reviews

Related threats