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

Source: https://junglewise.ai/threats/cve-2025-59017-typo3-backend-modules-have-broken-access-control  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2025-09-09  
License: CC BY 4.0 with a link back

CVE-2025-59017 · Severity: medium · CVSS 4 · Published 2025-09-09

TYPO3 backend modules have Broken Access Control

Technologies: [typo3/cms-backend (Packagist)](https://junglewise.ai/threats/technologies/typo3-cms-backend), [typo3/cms-recycler (Packagist)](https://junglewise.ai/threats/technologies/typo3-cms-recycler). Vendors: [Packagist](https://junglewise.ai/threats/vendors/packagist).

## Quick answers

**Is CVE-2025-59017 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2025-59017 being exploited in the wild.

**How severe is CVE-2025-59017?** Medium severity, with a CVSS score of 4, published 9 September 2025.

**Which products and versions are affected?** typo3/cms-backend (Packagist) ECOSYSTEM:introduced=9.0.0,fixed=12.4.37; typo3/cms-beuser (Packagist) ECOSYSTEM:introduced=13.0.0,fixed=13.4.18; typo3/cms-dashboard (Packagist) ECOSYSTEM:introduced=10.0.0,fixed=12.4.37; typo3/cms-recycler (Packagist) ECOSYSTEM:introduced=9.0.0,fixed=12.4.37; and 1 more.

**Is there a fix for CVE-2025-59017?** Yes. typo3/cms-backend (Packagist): upgrade to 12.4.37 or later; typo3/cms-beuser (Packagist): upgrade to 13.4.18 or later; typo3/cms-dashboard (Packagist): upgrade to 12.4.37 or later; typo3/cms-recycler (Packagist): upgrade to 12.4.37 or later; typo3/cms-workspaces (Packagist): upgrade to 12.4.37 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**Am I affected by CVE-2025-59017?** Check whether you run typo3/cms-backend (Packagist), typo3/cms-beuser (Packagist), typo3/cms-dashboard (Packagist) or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- typo3/cms-backend (Packagist): upgrade to 12.4.37 or later

  ```sh
  composer require typo3/cms-backend:^12.4.37
  ```

- typo3/cms-beuser (Packagist): upgrade to 13.4.18 or later

  ```sh
  composer require typo3/cms-beuser:^13.4.18
  ```

- typo3/cms-dashboard (Packagist): upgrade to 12.4.37 or later

  ```sh
  composer require typo3/cms-dashboard:^12.4.37
  ```

- typo3/cms-recycler (Packagist): upgrade to 12.4.37 or later

  ```sh
  composer require typo3/cms-recycler:^12.4.37
  ```

- typo3/cms-workspaces (Packagist): upgrade to 12.4.37 or later

  ```sh
  composer require typo3/cms-workspaces:^12.4.37
  ```


## Affected products

- typo3/cms-backend (Packagist) ECOSYSTEM:introduced=9.0.0,fixed=12.4.37
- typo3/cms-beuser (Packagist) ECOSYSTEM:introduced=13.0.0,fixed=13.4.18
- typo3/cms-dashboard (Packagist) ECOSYSTEM:introduced=10.0.0,fixed=12.4.37
- typo3/cms-recycler (Packagist) ECOSYSTEM:introduced=9.0.0,fixed=12.4.37
- typo3/cms-workspaces (Packagist) ECOSYSTEM:introduced=9.0.0,fixed=12.4.37

## Identifiers

- CVE-2025-59017
- GHSA-2fhw-2j7m-mr4m

## Related threats

- [The referrer enforcement introduced with TYPO3-CORE-SA-2020-006 became ineffective in TYPO3 v13.0, where TYPO3 CMS started](https://junglewise.ai/threats/cve-2026-19418-typo3-cms-broken-access-control-in-backend-and-install-tool)
- [TYPO3 CMS broken access control in Backend API](https://junglewise.ai/threats/cve-2026-47352-typo3-cms-broken-access-control-in-backend-api)
- [TYPO3 CMS broken access control in Clipboard](https://junglewise.ai/threats/cve-2026-47351-typo3-cms-broken-access-control-in-clipboard)
- [TYPO3 CMS missing authorization in Recycler module](https://junglewise.ai/threats/cve-2026-47349-typo3-cms-missing-authorization-in-recycler-module)
- [TYPO3 CMS Stores Cleartext Password in User Settings Module](https://junglewise.ai/threats/cve-2026-6553-typo3-cms-stores-cleartext-password-in-user-settings-module)