dbcve.org
TYPO3CMS

CVE-2025-59018

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 9.5.55 / 10.4.54 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
Missing authorization checks in the Workspace Module 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 the corresponding AJAX backend route to disclose sensitive information without having access.

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 confidence

TYPO3 CMS Workspace Module has missing authorization checks in AJAX backend routes, allowing authenticated backend users without proper workspace permissions to directly invoke these endpoints and disclose sensitive information. This is a broken access control vulnerability where the authorization verification is not enforced before processing requests to workspace-related AJAX actions.

MitigationApply the vendor-released security updates (TYPO3 versions 9.5.55, 10.4.54, 11.5.48, 12.4.37, and 13.4.18 or later) which include proper authorization checks for the Workspace Module AJAX endpoints. After patching, verify that workspace access controls function correctly.

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
Affected:>= 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.18

CVSS 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
None
Availability
None

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check TYPO3 CMS installed version
    Access the TYPO3 admin backend and navigate to 'About' in the help menu, or check the Composer.lock file or typo3/sysext/core/Composer.json for the installed version
    Affected if The installed version falls within any of these ranges: 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, or 13.0.0 to 13.4.17
  2. Verify Workspace extension is installed and enabled
    In the TYPO3 backend, go to 'Admin Tools' > 'Extensions' and confirm the 'workspaces' system extension is listed as active, or check the typo3/sysext/workspaces directory exists in the installation
    Affected if The Workspace extension is installed and enabled on a TYPO3 version within the affected ranges listed above
  3. Identify vulnerable Workspace AJAX endpoints
    Examine the AJAX controllers in the workspaces extension, specifically files under typo3/sysext/workspaces/Classes/Controller/ and look for ActionController or AjaxController classes handling workspace operations
    Affected if The workspace AJAX endpoints do not perform authorization checks before processing requests - they should verify user workspace permissions but currently do not
  4. Test access control on Workspace AJAX routes
    Using a browser developer tool or HTTP client, attempt to invoke Workspace AJAX endpoints (such as those under /typo3/ajax/workspaces/) with a backend user account that lacks workspace permissions
    Affected if The AJAX requests execute successfully and return sensitive workspace data (such as workspace preview content, stage information, or version history) without returning an authorization error

A user is affected if they run any TYPO3 version from 9.0.0 through the versions listed (9.5.54, 10.4.53, 11.5.47, 12.4.36, or 13.4.17) with the Workspace extension enabled, and the Workspace AJAX endpoints can be accessed without proper permission checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 9.5.55 / 10.4.54 / 11.5.48 or later
Fixed in 9.5.5510.4.5411.5.48
Interim mitigation

Apply the vendor-released security updates (TYPO3 versions 9.5.55, 10.4.54, 11.5.48, 12.4.37, and 13.4.18 or later) which include proper authorization checks for the Workspace Module AJAX endpoints. After patching, verify that workspace access controls function correctly.

Recommended fix High confidence

Upgrade to TYPO3 version 9.5.55, 10.4.54, 11.5.48, or 12.4.37 depending on your current major version branch

  1. 1. Identify the currently installed TYPO3 version by checking the composer.json or the Install Tool under 'Important > Installed Extensions'
  2. 2. Create a complete backup of the database and all files, including the composer.json and composer.lock files
  3. 3. For Composer-based installations, run: composer require typo3/cms-core:^10.4.54 --no-interaction (adjust the version number based on your current major version: 9.5.55, 10.4.54, 11.5.48, or 12.4.37)
  4. 4. Clear all caches after the upgrade by removing the var/cache directory or using the Install Tool's 'Clear Cache' function
  5. 5. Verify the upgrade was successful by checking the TYPO3 version in the Install Tool under 'Important > Installed Extensions'
  6. 6. Test that the Workspace Module still functions correctly and that unauthorized users can no longer access AJAX routes without proper permissions
Caveat Upgrading across major TYPO3 versions (e.g., 9.x to 10.x) may require code adjustments due to breaking changes; consult the TYPO3 changelog and upgrade guide for your target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in TYPO3 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59018 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59018 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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