CVE-2025-59021: TYPO3 CMS · Missing 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, 17:16 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 18% 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:L/VI:L/VA:L/SC:N/SI:N/SA:NExploitation 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.
What to do
Upgrade to a fixed release listed under Affected software.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| TYPO3TYPO3 CMS | Affected
| Fixed in
|
| TYPO3TYPO3 CMS | Affected
| Fixed in
|
| TYPO3TYPO3 CMS | Affected
| Fixed in
|
| TYPO3TYPO3 CMS | Affected
| Fixed in
|
| TYPO3TYPO3 CMS | Affected
| Fixed in
|
Packagisttypo3/cms-redirectspkg:composer/typo3/cms-redirectsOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
- Upgrade TYPO3 CMS to the latest patched version beyond 14.0.1 once available, as the vendor will likely release a fix addressing this authorization flaw.
- If you cannot patch yet, restrict backend user permissions by limiting access to the redirects module and write permissions on the sys_redirect table only to trusted administrators.
- Implement strict role-based access control (RBAC) to ensure users cannot modify redirects outside their scope.
- Monitor backend user activity logs for unusual redirect creation or modification patterns.
- Employ multi-factor authentication (MFA) for backend access to reduce risk of credential compromise.
- Conduct regular audits of redirect records to detect unauthorized or suspicious entries.
- Educate administrators about the risk of phishing via malicious redirects and encourage vigilance.
- Consider network segmentation or additional access controls to limit backend access to trusted networks.
- Use web application firewalls (WAF) to detect and block suspicious redirect patterns if possible.
- Maintain an incident response plan to quickly address any detected misuse of redirects.
Description
Backend users with access to the redirects module and write permission on the sys_redirect table were able to read, create, and modify any redirect record without restriction to the user’s own file-mounts or web-mounts. This allowed attackers to insert or alter redirects pointing to arbitrary URLs – facilitating phishing or other malicious redirect attacks. 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.
References
- typo3.org/security/advisory/typo3-core-sa-2026-002 (opens in a new tab)
- github.com/TYPO3/typo3/commit/8a46abd8993e3a5a31a834dcd6c8f91adef57ce4 (opens in a new tab)
- github.com/TYPO3/typo3/commit/bac370df5c1c3fcf5ebc1c030fbd2bec86d6a686 (opens in a new tab)
- github.com/TYPO3/typo3/commit/fbbae3b9a40d0420207ef7af990cdf1ac0612c0b (opens in a new tab)