CVE-2025-59022VulnerabilityPublished 13 Jan 2026

CVE-2025-59022: TYPO3 CMS · Missing Authorization

Affects TYPO3 CMSSource CVE Database V5

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

Data as of 26 Oct 2026, 06:26 UTC

CVSS 4.0 base score

7.1High

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

EPSS: 0.4% chance of exploitation in 30 days – higher than 35% 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:N/VA:H/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: None
Vulnerable system availability: High
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: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
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 2026-10-26.

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	Fixed in–
Packagisttypo3/cms-recycler`pkg:composer/typo3/cms-recycler`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

Organizations should immediately audit backend user permissions and restrict access to the recycler module to only the most trusted administrators. If possible, disable the recycler module temporarily until patches are applied. TYPO3 CMS maintainers should be monitored for official patches or updates addressing CVE-2025-59022, and these should be applied promptly across all affected versions. Implement strict backend user account management, including multi-factor authentication and regular credential reviews, to reduce the risk of compromised accounts. Enable detailed logging and monitoring of deletion activities within the CMS to detect suspicious behavior early. Consider network segmentation and access controls to limit backend access to trusted networks and personnel. Backup strategies should be reviewed and tested to ensure rapid recovery from data deletion incidents. Finally, educate administrators about the risks of this vulnerability and the importance of limiting backend module access.

Description

Backend users who had access to the recycler module could delete arbitrary data from any database table defined in the TCA - regardless of whether they had permission to that particular table. This allowed attackers to purge and destroy critical site data, effectively rendering the website unavailable. 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 using TYPO3 CMS, this vulnerability can lead to severe operational disruption. Attackers or malicious insiders with backend access can delete critical site data, causing loss of content, configuration, and potentially user information. This can result in website downtime, loss of public trust, and costly recovery efforts. Public sector entities relying on TYPO3 for citizen-facing portals are especially at risk, as service unavailability can impact government operations and citizen services. Enterprises using TYPO3 for e-commerce or internal portals may face financial losses and reputational damage. The broad range of affected TYPO3 versions means many organizations may be vulnerable if they have not applied updates. Since exploitation requires only backend user access, compromised or malicious internal accounts significantly increase risk. The lack of user interaction or complex exploitation steps means attacks could be automated or performed quickly once access is obtained. Overall, the vulnerability threatens confidentiality (due to unauthorized data access), integrity (due to data deletion), and availability (due to site disruption), with availability impact being the most critical.

CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
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)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (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:25 UTC

WeaknessesCWE-862

Technical details

References

Community reviews

Related threats