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
composer require typo3/cms-backend:^12.4.37
typo3/cms-beuser (Packagist): upgrade to 13.4.18 or later
composer require typo3/cms-beuser:^13.4.18
typo3/cms-dashboard (Packagist): upgrade to 12.4.37 or later
composer require typo3/cms-dashboard:^12.4.37
typo3/cms-recycler (Packagist): upgrade to 12.4.37 or later
composer require typo3/cms-recycler:^12.4.37
typo3/cms-workspaces (Packagist): upgrade to 12.4.37 or later