CVE-2025-59017 Broken Access Control in Backend AJAX Routes

Medium 5.3 Published Updated

Backend users can invoke AJAX routes without proper module access, bypassing authorization controls in TYPO3 CMS.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

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

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.

PackageAffectedFixed in
typo3/cms-backend PackagistFrom 10.0.012.4.37
typo3/cms-backend PackagistFrom 10.0.012.4.37
typo3/cms-backend PackagistFrom 11.0.012.4.37
typo3/cms-backend PackagistFrom 11.0.012.4.37
typo3/cms-backend PackagistFrom 12.0.012.4.37
typo3/cms-backend PackagistFrom 12.0.012.4.37
34 more packages
typo3/cms-backend PackagistFrom 13.0.013.4.18
typo3/cms-backend PackagistFrom 13.0.013.4.18
typo3/cms-backend PackagistFrom 9.0.012.4.37
typo3/cms-backend PackagistFrom 9.0.012.4.37
typo3/cms-beuser PackagistFrom 10.0.012.4.37
typo3/cms-beuser PackagistFrom 10.0.012.4.37
typo3/cms-beuser PackagistFrom 11.0.012.4.37
typo3/cms-beuser PackagistFrom 11.0.012.4.37
typo3/cms-beuser PackagistFrom 12.0.012.4.37
typo3/cms-beuser PackagistFrom 12.0.012.4.37
typo3/cms-beuser PackagistFrom 13.0.013.4.18
typo3/cms-beuser PackagistFrom 13.0.013.4.18
typo3/cms-beuser PackagistFrom 9.0.012.4.37
typo3/cms-beuser PackagistFrom 9.0.012.4.37
typo3/cms-dashboard PackagistFrom 10.0.012.4.37
typo3/cms-dashboard PackagistFrom 10.0.012.4.37
typo3/cms-dashboard PackagistFrom 11.0.012.4.37
typo3/cms-dashboard PackagistFrom 11.0.012.4.37
typo3/cms-dashboard PackagistFrom 12.0.012.4.37
typo3/cms-dashboard PackagistFrom 12.0.012.4.37
typo3/cms-dashboard PackagistFrom 13.0.013.4.18
typo3/cms-dashboard PackagistFrom 13.0.013.4.18
typo3/cms-recycler PackagistFrom 10.0.012.4.37
typo3/cms-recycler PackagistFrom 10.0.012.4.37
typo3/cms-recycler PackagistFrom 11.0.012.4.37
typo3/cms-recycler PackagistFrom 11.0.012.4.37
typo3/cms-recycler PackagistFrom 12.0.012.4.37
typo3/cms-recycler PackagistFrom 12.0.012.4.37
typo3/cms-recycler PackagistFrom 13.0.013.4.18
typo3/cms-recycler PackagistFrom 13.0.013.4.18
typo3/cms-recycler PackagistFrom 9.0.012.4.37
typo3/cms-recycler PackagistFrom 9.0.012.4.37
typo3/cms-workspaces PackagistFrom 10.0.012.4.37
typo3/cms-workspaces PackagistFrom 10.0.012.4.37

Products include 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.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2025-59017 being exploited?

There is no known exploitation of CVE-2025-59017 in the wild and no public exploit code.

All Typo3 Typo3 vulnerabilities

Sources

Also known as GHSA-2fhw-2j7m-mr4m.

Is CVE-2025-59017 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free