Summary
An open‑redirect vulnerability in GeneralUtility::sanitizeLocalUrl of TYPO3 CMS 9.0.0–9.5.54, 10.0.0–10.4.53, 11.0.0–11.5.47, 12.0.0–12.4.36, and 13.0.0–13.4.17 allows an attacker to redirect users to arbitrary external sites, enabling phishing attacks by supplying a manipulated, sanitized URL.
Impact
Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites. Typical impact: phishing and credential harvesting via a trusted domain.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
typo3/cms-core to 12.4.37 or later; typo3/cms-core to 12.4.37 or later; typo3/cms-core to 12.4.37 or later; typo3/cms-core to 12.4.37 or later; typo3/cms-core to 13.4.18 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2025-59013? CVE-2025-59013 is a medium-severity open redirect vulnerability in typo3/cms-core (composer), affecting versions >= 9.0.0, < 9.5.55. It is fixed in 12.4.37, 13.4.18. Untrusted input controls a URL used for redirection, which can forward users to attacker-controlled sites.
- Which versions of typo3/cms-core are affected by CVE-2025-59013? typo3/cms-core (composer) versions >= 9.0.0, < 9.5.55 is affected.
- Is there a fix for CVE-2025-59013? Yes. CVE-2025-59013 is fixed in 12.4.37, 13.4.18. Upgrade to this version or later.
- Is CVE-2025-59013 exploitable, and should I be worried? Whether CVE-2025-59013 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-59013 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-59013?
- Upgrade
typo3/cms-coreto 12.4.37 or later - Upgrade
typo3/cms-coreto 12.4.37 or later - Upgrade
typo3/cms-coreto 12.4.37 or later - Upgrade
typo3/cms-coreto 12.4.37 or later - Upgrade
typo3/cms-coreto 13.4.18 or later
- Upgrade