CVE-2025-59017: TYPO3 backend modules have Broken Access Control

Published Sep 9, 2025
·
Updated

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.

Other sources

TYPO3 backend modules have Broken Access Control

— Packagist

Affected Software

54 affected componentsFixes available
Typo3 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, >=13.0.0<=13.4.17
composer/typo3/cms-backend>=13.0.0<13.4.18
13.4.18
composer/typo3/cms-backend>=12.0.0<12.4.37
12.4.37
composer/typo3/cms-backend>=11.0.0<11.5.48
12.4.37
composer/typo3/cms-backend>=10.0.0<10.4.54
12.4.37
composer/typo3/cms-backend>=9.0.0<9.5.55
12.4.37
composer/typo3/cms-beuser>=9.0.0<9.5.55
12.4.37
composer/typo3/cms-beuser>=10.0.0<10.4.54
12.4.37
composer/typo3/cms-beuser>=11.0.0<11.5.48
12.4.37
composer/typo3/cms-beuser>=12.0.0<12.4.37
12.4.37
composer/typo3/cms-beuser>=13.0.0<13.4.18
13.4.18
composer/typo3/cms-dashboard>=13.0.0<13.4.18
13.4.18
composer/typo3/cms-dashboard>=12.0.0<12.4.37
12.4.37
composer/typo3/cms-dashboard>=11.0.0<11.5.48
12.4.37
composer/typo3/cms-dashboard>=10.0.0<10.4.54
12.4.37
composer/typo3/cms-recycler>=13.0.0<13.4.18
13.4.18
composer/typo3/cms-recycler>=12.0.0<12.4.37
12.4.37
composer/typo3/cms-recycler>=11.0.0<11.5.48
12.4.37
composer/typo3/cms-recycler>=10.0.0<10.4.54
12.4.37
composer/typo3/cms-recycler>=9.0.0<9.5.55
12.4.37
composer/typo3/cms-workspaces>=13.0.0<13.4.18
13.4.18
composer/typo3/cms-workspaces>=12.0.0<12.4.37
12.4.37
composer/typo3/cms-workspaces>=11.0.0<11.5.48
12.4.37
composer/typo3/cms-workspaces>=10.0.0<10.4.54
12.4.37
composer/typo3/cms-workspaces>=9.0.0<9.5.55
12.4.37
Typo3 TYPO3>=9.0.0<9.5.55
Typo3 TYPO3>=10.0.0<10.4.54
Typo3 TYPO3>=11.0.0<11.5.48
Typo3 TYPO3>=12.0.0<12.4.37
Typo3 TYPO3>=13.0.0<13.4.18
composer/typo3/cms-backend>=13.0.0, <13.4.18
13.4.18
composer/typo3/cms-backend>=12.0.0, <12.4.37
12.4.37
composer/typo3/cms-backend>=11.0.0, <11.5.48
11.5.48
composer/typo3/cms-backend>=10.0.0, <10.4.54
10.4.54
composer/typo3/cms-backend>=9.0.0, <9.5.55
9.5.55
composer/typo3/cms-recycler>=13.0.0, <13.4.18
13.4.18
composer/typo3/cms-recycler>=12.0.0, <12.4.37
12.4.37
composer/typo3/cms-recycler>=11.0.0, <11.5.48
11.5.48
composer/typo3/cms-recycler>=10.0.0, <10.4.54
10.4.54
composer/typo3/cms-recycler>=9.0.0, <9.5.55
9.5.55
composer/typo3/cms-beuser>=9.0.0, <9.5.55
9.5.55
composer/typo3/cms-beuser>=10.0.0, <10.4.54
10.4.54
composer/typo3/cms-beuser>=11.0.0, <11.5.48
11.5.48
composer/typo3/cms-beuser>=12.0.0, <12.4.37
12.4.37
composer/typo3/cms-beuser>=13.0.0, <13.4.18
13.4.18
composer/typo3/cms-workspaces>=13.0.0, <13.4.18
13.4.18
composer/typo3/cms-workspaces>=12.0.0, <12.4.37
12.4.37
composer/typo3/cms-workspaces>=11.0.0, <11.5.48
11.5.48
composer/typo3/cms-workspaces>=10.0.0, <10.4.54
10.4.54
composer/typo3/cms-workspaces>=9.0.0, <9.5.55
9.5.55
composer/typo3/cms-dashboard>=13.0.0, <13.4.18
13.4.18
composer/typo3/cms-dashboard>=12.0.0, <12.4.37
12.4.37
composer/typo3/cms-dashboard>=11.0.0, <11.5.48
11.5.48
composer/typo3/cms-dashboard>=10.0.0, <10.4.54
10.4.54

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/typo3/cms-backend to a version that resolves this vulnerability.

    Fixed in 13.4.18
  2. Upgrade

    Upgrade composer/typo3/cms-backend to a version that resolves this vulnerability.

    Fixed in 12.4.37
  3. Upgrade

    Upgrade composer/typo3/cms-beuser to a version that resolves this vulnerability.

    Fixed in 12.4.37
  4. Upgrade

    Upgrade composer/typo3/cms-beuser to a version that resolves this vulnerability.

    Fixed in 13.4.18
  5. Upgrade

    Upgrade composer/typo3/cms-dashboard to a version that resolves this vulnerability.

    Fixed in 13.4.18
  6. Upgrade

    Upgrade composer/typo3/cms-dashboard to a version that resolves this vulnerability.

    Fixed in 12.4.37
  7. Upgrade

    Upgrade composer/typo3/cms-recycler to a version that resolves this vulnerability.

    Fixed in 13.4.18
  8. Upgrade

    Upgrade composer/typo3/cms-recycler to a version that resolves this vulnerability.

    Fixed in 12.4.37
  9. Upgrade

    Upgrade composer/typo3/cms-workspaces to a version that resolves this vulnerability.

    Fixed in 13.4.18
  10. Upgrade

    Upgrade composer/typo3/cms-workspaces to a version that resolves this vulnerability.

    Fixed in 12.4.37
  11. Upgrade

    Upgrade composer/typo3/cms-backend to a version that resolves this vulnerability.

    Fixed in 11.5.48
  12. Upgrade

    Upgrade composer/typo3/cms-backend to a version that resolves this vulnerability.

    Fixed in 10.4.54
  13. Upgrade

    Upgrade composer/typo3/cms-backend to a version that resolves this vulnerability.

    Fixed in 9.5.55
  14. Upgrade

    Upgrade composer/typo3/cms-recycler to a version that resolves this vulnerability.

    Fixed in 11.5.48
  15. Upgrade

    Upgrade composer/typo3/cms-recycler to a version that resolves this vulnerability.

    Fixed in 10.4.54
  16. Upgrade

    Upgrade composer/typo3/cms-recycler to a version that resolves this vulnerability.

    Fixed in 9.5.55
  17. Upgrade

    Upgrade composer/typo3/cms-dashboard to a version that resolves this vulnerability.

    Fixed in 11.5.48
  18. Upgrade

    Upgrade composer/typo3/cms-dashboard to a version that resolves this vulnerability.

    Fixed in 10.4.54
  19. Upgrade

    Upgrade composer/typo3/cms-beuser to a version that resolves this vulnerability.

    Fixed in 9.5.55
  20. Upgrade

    Upgrade composer/typo3/cms-beuser to a version that resolves this vulnerability.

    Fixed in 10.4.54
  21. Upgrade

    Upgrade composer/typo3/cms-beuser to a version that resolves this vulnerability.

    Fixed in 11.5.48
  22. Upgrade

    Upgrade composer/typo3/cms-workspaces to a version that resolves this vulnerability.

    Fixed in 11.5.48
  23. Upgrade

    Upgrade composer/typo3/cms-workspaces to a version that resolves this vulnerability.

    Fixed in 10.4.54
  24. Upgrade

    Upgrade composer/typo3/cms-workspaces to a version that resolves this vulnerability.

    Fixed in 9.5.55

Event History

Sep 9, 2025
CVE Published
via MITRE·09:01 AM
Data Sourced
via MITRE·09:01 AM
DescriptionWeakness
Data Sourced
via NVD·09:15 AM
DescriptionSeverityWeaknessAffected Software
Advisory Published
via GitHub·09:31 AM
Data Sourced
via GitHub·09:31 AM
DescriptionWeaknessAffected Software
Data Sourced
via Packagist·09:31 AM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2025-59017?

CVE-2025-59017 has a medium severity rating due to missing authorization checks in the backend routing.

2

How do I fix CVE-2025-59017?

To fix CVE-2025-59017, you should upgrade TYPO3 CMS to a version that is not affected by this vulnerability.

3

Which versions of TYPO3 CMS are vulnerable to CVE-2025-59017?

CVE-2025-59017 affects TYPO3 CMS versions 9.0.0 to 9.5.54, 10.0.0 to 10.4.53, 11.0.0 to 11.5.47, 12.0.0 to 12.4.36, and 13.0.0 to 13.4.17.

4

What type of attack does CVE-2025-59017 enable?

CVE-2025-59017 enables unauthorized backend users to invoke AJAX backend routes without appropriate access.

5

Is my system safe if I am using a patched version of TYPO3 CMS regarding CVE-2025-59017?

Yes, if you are using a patched version of TYPO3 CMS, your system is safe from the vulnerabilities associated with CVE-2025-59017.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203