# CVE-2025-59017: Broken Access Control in Backend AJAX Routes > Backend users can invoke AJAX routes without proper module access, bypassing authorization controls in TYPO3 CMS. - **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Sep 2025 - **Updated:** 9 Sep 2025 - **Also known as:** GHSA-2fhw-2j7m-mr4m ## What is CVE-2025-59017? CVE-2025-59017 is a medium-severity missing authorization vulnerability in Typo3 Typo3, published on 9 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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. Weakness: CWE-862 (Missing Authorization) ## Which versions are affected by CVE-2025-59017? 40 open source packages ship an affected version, including typo3/cms-backend, typo3/cms-beuser and typo3/cms-dashboard. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `typo3/cms-backend` | Packagist | From 10.0.0 | 12.4.37 | | `typo3/cms-backend` | Packagist | From 10.0.0 | 12.4.37 | | `typo3/cms-backend` | Packagist | From 11.0.0 | 12.4.37 | | `typo3/cms-backend` | Packagist | From 11.0.0 | 12.4.37 | | `typo3/cms-backend` | Packagist | From 12.0.0 | 12.4.37 | | `typo3/cms-backend` | Packagist | From 12.0.0 | 12.4.37 | | `typo3/cms-backend` | Packagist | From 13.0.0 | 13.4.18 | | `typo3/cms-backend` | Packagist | From 13.0.0 | 13.4.18 | | `typo3/cms-backend` | Packagist | From 9.0.0 | 12.4.37 | | `typo3/cms-backend` | Packagist | From 9.0.0 | 12.4.37 | | `typo3/cms-beuser` | Packagist | From 10.0.0 | 12.4.37 | | `typo3/cms-beuser` | Packagist | From 10.0.0 | 12.4.37 | | `typo3/cms-beuser` | Packagist | From 11.0.0 | 12.4.37 | | `typo3/cms-beuser` | Packagist | From 11.0.0 | 12.4.37 | | `typo3/cms-beuser` | Packagist | From 12.0.0 | 12.4.37 | | `typo3/cms-beuser` | Packagist | From 12.0.0 | 12.4.37 | | `typo3/cms-beuser` | Packagist | From 13.0.0 | 13.4.18 | | `typo3/cms-beuser` | Packagist | From 13.0.0 | 13.4.18 | | `typo3/cms-beuser` | Packagist | From 9.0.0 | 12.4.37 | | `typo3/cms-beuser` | Packagist | From 9.0.0 | 12.4.37 | | `typo3/cms-dashboard` | Packagist | From 10.0.0 | 12.4.37 | | `typo3/cms-dashboard` | Packagist | From 10.0.0 | 12.4.37 | | `typo3/cms-dashboard` | Packagist | From 11.0.0 | 12.4.37 | | `typo3/cms-dashboard` | Packagist | From 11.0.0 | 12.4.37 | | `typo3/cms-dashboard` | Packagist | From 12.0.0 | 12.4.37 | | `typo3/cms-dashboard` | Packagist | From 12.0.0 | 12.4.37 | | `typo3/cms-dashboard` | Packagist | From 13.0.0 | 13.4.18 | | `typo3/cms-dashboard` | Packagist | From 13.0.0 | 13.4.18 | | `typo3/cms-recycler` | Packagist | From 10.0.0 | 12.4.37 | | `typo3/cms-recycler` | Packagist | From 10.0.0 | 12.4.37 | | `typo3/cms-recycler` | Packagist | From 11.0.0 | 12.4.37 | | `typo3/cms-recycler` | Packagist | From 11.0.0 | 12.4.37 | | `typo3/cms-recycler` | Packagist | From 12.0.0 | 12.4.37 | | `typo3/cms-recycler` | Packagist | From 12.0.0 | 12.4.37 | | `typo3/cms-recycler` | Packagist | From 13.0.0 | 13.4.18 | | `typo3/cms-recycler` | Packagist | From 13.0.0 | 13.4.18 | | `typo3/cms-recycler` | Packagist | From 9.0.0 | 12.4.37 | | `typo3/cms-recycler` | Packagist | From 9.0.0 | 12.4.37 | | `typo3/cms-workspaces` | Packagist | From 10.0.0 | 12.4.37 | | `typo3/cms-workspaces` | Packagist | From 10.0.0 | 12.4.37 | Products: Typo3 Typo3. ## How do I fix CVE-2025-59017? Upgrade typo3/cms-backend to a fixed version for your release line: 12.4.37 or 13.4.18. ## Is CVE-2025-59017 being exploited? There is no known exploitation of CVE-2025-59017 in the wild and no public exploit code. ## Other vulnerabilities in Typo3 Typo3 - [CVE-2009-0258](https://insights.sbomify.com/CVE-2009-0258/): Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection (critical 10.0) - [CVE-2011-3583](https://insights.sbomify.com/CVE-2011-3583/): Typo3 SQL injection due to faulty prepared statements (critical 9.8) - [CVE-2011-4628](https://insights.sbomify.com/CVE-2011-4628/): Typo3 Authentication Bypass (critical 9.8) - [CVE-2023-24814](https://insights.sbomify.com/CVE-2023-24814/): Persisted Cross-Site Scripting in Frontend Rendering in typo3 (high 8.8) - [CVE-2021-41113](https://insights.sbomify.com/CVE-2021-41113/): Cross-Site-Request-Forgery in Backend URI Handling in Typo3 (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2025-59017 and fix it if it is affected. What it is: CVE-2025-59017 is a medium-severity missing authorization vulnerability in Typo3 Typo3, published on 9 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2025-59017 in the wild and no public exploit code. Affected packages and fixed versions: - typo3/cms-backend (Packagist): affected from 10.0.0; fixed in 12.4.37 - typo3/cms-backend (Packagist): affected from 10.0.0; fixed in 12.4.37 - typo3/cms-backend (Packagist): affected from 11.0.0; fixed in 12.4.37 - typo3/cms-backend (Packagist): affected from 11.0.0; fixed in 12.4.37 - typo3/cms-backend (Packagist): affected from 12.0.0; fixed in 12.4.37 - typo3/cms-backend (Packagist): affected from 12.0.0; fixed in 12.4.37 - typo3/cms-backend (Packagist): affected from 13.0.0; fixed in 13.4.18 - typo3/cms-backend (Packagist): affected from 13.0.0; fixed in 13.4.18 - typo3/cms-backend (Packagist): affected from 9.0.0; fixed in 12.4.37 - typo3/cms-backend (Packagist): affected from 9.0.0; fixed in 12.4.37 - typo3/cms-beuser (Packagist): affected from 10.0.0; fixed in 12.4.37 - typo3/cms-beuser (Packagist): affected from 10.0.0; fixed in 12.4.37 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2025-59017/ (Markdown: https://insights.sbomify.com/CVE-2025-59017/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59017 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59017 - OSV: https://osv.dev/vulnerability/CVE-2025-59017 --- From sbomify Insights: https://insights.sbomify.com/CVE-2025-59017/ Summaries are generated and may contain mistakes; the official description above is the record.