What is CVE-2025-59017?

CVE-2025-59017 is a medium-severity missing authorization vulnerability in typo3/cms-workspaces (composer), affecting versions >= 9.0.0, < 9.5.55. It is fixed in 12.4.37, 13.4.18. The application does not perform an authorization check before performing a sensitive operation.

Which packages are affected by CVE-2025-59017?

typo3/cms-workspaces (composer) versions >= 9.0.0, = 9.0.0, = 10.0.0, = 13.0.0, = 9.0.0, < 9.5.55.

Is there a fix for CVE-2025-59017?

Yes. CVE-2025-59017 is fixed in 12.4.37, 13.4.18. Upgrade to this version or later.

Is CVE-2025-59017 exploitable, and should I be worried?

Whether CVE-2025-59017 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.

What actually determines whether CVE-2025-59017 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.

CVE-2025-59017 in typo3/cms-workspaces | Intelligent Application Security

Q: Which packages are affected by CVE-2025-59017?

typo3/cms-workspaces (composer) versions >= 9.0.0, = 9.0.0, = 10.0.0, = 13.0.0, = 9.0.0, < 9.5.55.

Q: Is there a fix for CVE-2025-59017?

Yes. CVE-2025-59017 is fixed in 12.4.37, 13.4.18. Upgrade to this version or later.

Q: Is CVE-2025-59017 exploitable, and should I be worried?

Whether CVE-2025-59017 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.

Q: What actually determines whether CVE-2025-59017 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.

Q: How do I fix CVE-2025-59017?

Upgrade: typo3/cms-workspaces to 12.4.37 or later, typo3/cms-workspaces to 12.4.37 or later, typo3/cms-workspaces to 12.4.37 or later, typo3/cms-workspaces to 12.4.37 or later, typo3/cms-workspaces to 13.4.18 or later, typo3/cms-recycler to 12.4.37 or later, typo3/cms-recycler to 12.4.37 or later, typo3/cms-recycler to 12.4.37 or later, typo3/cms-recycler to 12.4.37 or later, typo3/cms-recycler to 13.4.18 or later, typo3/cms-dashboard to 12.4.37 or later, typo3/cms-dashboard to 12.4.37 or later, typo3/cms-dashboard to 12.4.37 or later, typo3/cms-dashboard to 13.4.18 or later, typo3/cms-beuser to 13.4.18 or later, typo3/cms-beuser to 12.4.37 or later, typo3/cms-beuser to 12.4.37 or later, typo3/cms-beuser to 12.4.37 or later, typo3/cms-beuser to 12.4.37 or later, typo3/cms-backend to 12.4.37 or later, typo3/cms-backend to 12.4.37 or later, typo3/cms-backend to 12.4.37 or later, typo3/cms-backend to 12.4.37 or later, typo3/cms-backend to 13.4.18 or later.

Summary

Missing authorization checks in the Backend Routing of TYPO3 CMS versions 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 allow backend users to directly invoke AJAX backend routes without having access to the corresponding backend modules.

Impact

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

Affected versions

typo3/cms-workspaces (>= 9.0.0, < 9.5.55) typo3/cms-workspaces (>= 10.0.0, < 10.4.54) typo3/cms-workspaces (>= 11.0.0, < 11.5.48) typo3/cms-workspaces (>= 12.0.0, < 12.4.37) typo3/cms-workspaces (>= 13.0.0, < 13.4.18) typo3/cms-recycler (>= 9.0.0, < 9.5.55) typo3/cms-recycler (>= 10.0.0, < 10.4.54) typo3/cms-recycler (>= 11.0.0, < 11.5.48) typo3/cms-recycler (>= 12.0.0, < 12.4.37) typo3/cms-recycler (>= 13.0.0, < 13.4.18) typo3/cms-dashboard (>= 10.0.0, < 10.4.54) typo3/cms-dashboard (>= 11.0.0, < 11.5.48) typo3/cms-dashboard (>= 12.0.0, < 12.4.37) typo3/cms-dashboard (>= 13.0.0, < 13.4.18) typo3/cms-beuser (>= 13.0.0, < 13.4.18) typo3/cms-beuser (>= 12.0.0, < 12.4.37) typo3/cms-beuser (>= 11.0.0, < 11.5.48) typo3/cms-beuser (>= 10.0.0, < 10.4.54) typo3/cms-beuser (>= 9.0.0, < 9.5.55) typo3/cms-backend (>= 9.0.0, < 9.5.55) typo3/cms-backend (>= 10.0.0, < 10.4.54) typo3/cms-backend (>= 11.0.0, < 11.5.48) typo3/cms-backend (>= 12.0.0, < 12.4.37) typo3/cms-backend (>= 13.0.0, < 13.4.18)

Security releases

typo3/cms-workspaces → 12.4.37 (composer) typo3/cms-workspaces → 12.4.37 (composer) typo3/cms-workspaces → 12.4.37 (composer) typo3/cms-workspaces → 12.4.37 (composer) typo3/cms-workspaces → 13.4.18 (composer) typo3/cms-recycler → 12.4.37 (composer) typo3/cms-recycler → 12.4.37 (composer) typo3/cms-recycler → 12.4.37 (composer) typo3/cms-recycler → 12.4.37 (composer) typo3/cms-recycler → 13.4.18 (composer) typo3/cms-dashboard → 12.4.37 (composer) typo3/cms-dashboard → 12.4.37 (composer) typo3/cms-dashboard → 12.4.37 (composer) typo3/cms-dashboard → 13.4.18 (composer) typo3/cms-beuser → 13.4.18 (composer) typo3/cms-beuser → 12.4.37 (composer) typo3/cms-beuser → 12.4.37 (composer) typo3/cms-beuser → 12.4.37 (composer) typo3/cms-beuser → 12.4.37 (composer) typo3/cms-backend → 12.4.37 (composer) typo3/cms-backend → 12.4.37 (composer) typo3/cms-backend → 12.4.37 (composer) typo3/cms-backend → 12.4.37 (composer) typo3/cms-backend → 13.4.18 (composer)

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.

See it in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

typo3/cms-workspaces to 12.4.37 or later; typo3/cms-workspaces to 12.4.37 or later; typo3/cms-workspaces to 12.4.37 or later; typo3/cms-workspaces to 12.4.37 or later; typo3/cms-workspaces to 13.4.18 or later; typo3/cms-recycler to 12.4.37 or later; typo3/cms-recycler to 12.4.37 or later; typo3/cms-recycler to 12.4.37 or later; typo3/cms-recycler to 12.4.37 or later; typo3/cms-recycler to 13.4.18 or later; typo3/cms-dashboard to 12.4.37 or later; typo3/cms-dashboard to 12.4.37 or later; typo3/cms-dashboard to 12.4.37 or later; typo3/cms-dashboard to 13.4.18 or later; typo3/cms-beuser to 13.4.18 or later; typo3/cms-beuser to 12.4.37 or later; typo3/cms-beuser to 12.4.37 or later; typo3/cms-beuser to 12.4.37 or later; typo3/cms-beuser to 12.4.37 or later; typo3/cms-backend to 12.4.37 or later; typo3/cms-backend to 12.4.37 or later; typo3/cms-backend to 12.4.37 or later; typo3/cms-backend to 12.4.37 or later; typo3/cms-backend 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-59017? CVE-2025-59017 is a medium-severity missing authorization vulnerability in typo3/cms-workspaces (composer), affecting versions >= 9.0.0, < 9.5.55. It is fixed in 12.4.37, 13.4.18. The application does not perform an authorization check before performing a sensitive operation.
Which packages are affected by CVE-2025-59017?
- typo3/cms-workspaces (composer) (versions >= 9.0.0, < 9.5.55)
- typo3/cms-recycler (composer) (versions >= 9.0.0, < 9.5.55)
- typo3/cms-dashboard (composer) (versions >= 10.0.0, < 10.4.54)
- typo3/cms-beuser (composer) (versions >= 13.0.0, < 13.4.18)
- typo3/cms-backend (composer) (versions >= 9.0.0, < 9.5.55)
Is there a fix for CVE-2025-59017? Yes. CVE-2025-59017 is fixed in 12.4.37, 13.4.18. Upgrade to this version or later.
Is CVE-2025-59017 exploitable, and should I be worried? Whether CVE-2025-59017 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-59017 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-59017?
- Upgrade typo3/cms-workspaces to 12.4.37 or later
- Upgrade typo3/cms-workspaces to 12.4.37 or later
- Upgrade typo3/cms-workspaces to 12.4.37 or later
- Upgrade typo3/cms-workspaces to 12.4.37 or later
- Upgrade typo3/cms-workspaces to 13.4.18 or later
- Upgrade typo3/cms-recycler to 12.4.37 or later
- Upgrade typo3/cms-recycler to 12.4.37 or later
- Upgrade typo3/cms-recycler to 12.4.37 or later
- Upgrade typo3/cms-recycler to 12.4.37 or later
- Upgrade typo3/cms-recycler to 13.4.18 or later
- Upgrade typo3/cms-dashboard to 12.4.37 or later
- Upgrade typo3/cms-dashboard to 12.4.37 or later
- Upgrade typo3/cms-dashboard to 12.4.37 or later
- Upgrade typo3/cms-dashboard to 13.4.18 or later
- Upgrade typo3/cms-beuser to 13.4.18 or later
- Upgrade typo3/cms-beuser to 12.4.37 or later
- Upgrade typo3/cms-beuser to 12.4.37 or later
- Upgrade typo3/cms-beuser to 12.4.37 or later
- Upgrade typo3/cms-beuser to 12.4.37 or later
- Upgrade typo3/cms-backend to 12.4.37 or later
- Upgrade typo3/cms-backend to 12.4.37 or later
- Upgrade typo3/cms-backend to 12.4.37 or later
- Upgrade typo3/cms-backend to 12.4.37 or later
- Upgrade typo3/cms-backend to 13.4.18 or later

Other vulnerabilities in typo3/cms-workspaces

CVE-2025-59018