Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2025-59017

TYPO3 backend modules have Broken Access Control

Overview

Published
9 Sep 2025
Modified
17 Jun 2026
Medium CVE
5 Registry packages
0 OS packages
0 Linux distributions
Yes Fix available

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.

Source: OX vulnerability database

Severity

8.8 · MEDIUM

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Weakness: CWE-862

Affected packages · 5

Packages affected by CVE-2025-59017
EcosystemPackageVulnerableFixed in
Composer (PHP) typo3/cms-backend >=9.0.0, <12.4.37>=10.0.0, <12.4.37>=11.0.0, <12.4.37>=12.0.0, <12.4.37>=13.0.0, <13.4.18 12.4.3713.4.18
Composer (PHP) typo3/cms-beuser >=13.0.0, <13.4.18>=12.0.0, <12.4.37>=11.0.0, <12.4.37>=10.0.0, <12.4.37>=9.0.0, <12.4.37 13.4.1812.4.37
Composer (PHP) typo3/cms-dashboard >=10.0.0, <12.4.37>=11.0.0, <12.4.37>=12.0.0, <12.4.37>=13.0.0, <13.4.18 12.4.3713.4.18
Composer (PHP) typo3/cms-recycler >=9.0.0, <12.4.37>=10.0.0, <12.4.37>=11.0.0, <12.4.37>=12.0.0, <12.4.37>=13.0.0, <13.4.18 12.4.3713.4.18
Composer (PHP) typo3/cms-workspaces >=9.0.0, <12.4.37>=10.0.0, <12.4.37>=11.0.0, <12.4.37>=12.0.0, <12.4.37>=13.0.0, <13.4.18 12.4.3713.4.18

Open a package to see all its vulnerabilities.

Operating systems

No Linux distribution reports this ID.

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.