TYPO3CMS
CVE-2025-59017
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMissing 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceTYPO3 CMS fails to perform authorization checks on AJAX backend routes, allowing authenticated backend users to directly invoke these routes without verifying they have access to the corresponding backend modules. This enables privilege escalation where users with limited permissions can access functionality meant for higher-privilege roles.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
TYPO3CMS
>= 9.0.0, < 9.5.55>= 10.0.0, < 10.4.54>= 11.0.0, < 11.5.48>= 12.0.0, < 12.4.37>= 13.0.0, < 13.4.18CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- 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
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed TYPO3 CMS versionLocate the version file (typically in typo3/syseems/core/Classes/Information/Typo3Version.php or check composer.json) or log into the backend and navigate to Help > About to view the exact version numberAffected if version is within any of these ranges: >=9.0.0 and <9.5.55, >=10.0.0 and <10.4.54, >=11.0.0 and <11.5.48, >=12.0.0 and <12.4.37, or >=13.0.0 and <13.4.18
-
Verify backend user account privilegesIn the TYPO3 backend, go to Admin Tools > Users to review the permissions assigned to your backend user account. Determine whether your account has limited or restricted module accessAffected if your account has limited permissions but you can access AJAX backend routes directly
-
Test AJAX route accessibility with limited permissionsUsing a low-privilege backend user account, attempt to directly invoke AJAX endpoints (typically under /ajax/ or /ajax.php?route=) that correspond to privileged modules such as system maintenance, user management, or extension configurationAffected if a low-privilege user can successfully access AJAX routes meant for higher-privilege roles without receiving an access denied error
-
Inspect backend route configurationExamine the TYPO3 routing configuration files in typo3/syseems/backend/Resources/Private/Configuration/ and any custom route definitions in your extension to identify AJAX routesAffected if AJAX routes are defined without corresponding permission checks in the route definition
Your environment is affected if the installed TYPO3 version falls within any of the listed vulnerable ranges and low-privilege backend users can access AJAX routes that should require elevated permissions.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.5.5510.4.5411.5.48
Update TYPO3 CMS to versions 9.5.55, 10.4.54, 11.5.48, 12.4.37, 13.4.18 or later to patch the missing authorization checks in backend routing.
Upgrade to version 9.5.55 (v9 branch), 10.4.54 (v10 branch), 11.5.48 (v11 branch), or 12.4.37 (v12 branch) depending on your current branch
- 1. Identify the currently installed TYPO3 CMS version by checking the Composer.lock file or the install tool system information
- 2. Determine which version branch (9.x, 10.x, 11.x, or 12.x) your installation is running on
- 3. For TYPO3 v9.x: Upgrade to version 9.5.55 or later
- 4. For TYPO3 v10.x: Upgrade to version 10.4.54 or later
- 5. For TYPO3 v11.x: Upgrade to version 11.5.48 or later
- 6. For TYPO3 v12.x: Upgrade to version 12.4.37 or later
- 7. After upgrading, clear all caches via the Install Tool or CLI: rm -rf var/cache/*
- 8. Verify the upgrade was successful by checking the Backend and confirming the version number in the About module
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59017 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59017 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data