GHSA-2fhw-2j7m-mr4m — typo3/cms-workspaces
Fix: TYPO3-CMS/backend@0aedf33GHSA-2fhw-2j7m-mr4m is a CWE-862 vulnerability in typo3/cms-workspaces. A fix is available for typo3/cms-workspaces — see the affected versions and patch details below.
TYPO3 backend modules have Broken Access Control
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-2fhw-2j7m-mr4m.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Real-World Exposure
typo3/cms-workspaces🐘typo3/cms-workspaces🐘typo3/cms-workspaces🐘typo3/cms-workspaces🐘typo3/cms-workspaces🐘typo3/cms-recycler🐘typo3/cms-recycler🐘typo3/cms-recycler+16 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-workspaces | ≥ 9.0.0&&< 12.4.37 | 12.4.37composer require typo3/cms-workspaces:^12.4.37 |
| 🐘Packagist | typo3/cms-workspaces | ≥ 10.0.0&&< 12.4.37 | 12.4.37composer require typo3/cms-workspaces:^12.4.37 |
| 🐘Packagist | typo3/cms-workspaces | ≥ 11.0.0&&< 12.4.37 | 12.4.37composer require typo3/cms-workspaces:^12.4.37 |
| 🐘Packagist | typo3/cms-workspaces | ≥ 12.0.0&&< 12.4.37 | 12.4.37composer require typo3/cms-workspaces:^12.4.37 |
| 🐘Packagist | typo3/cms-workspaces | ≥ 13.0.0&&< 13.4.18 | 13.4.18composer require typo3/cms-workspaces:^13.4.18 |
| 🐘Packagist | typo3/cms-recycler | ≥ 9.0.0&&< 12.4.37 | 12.4.37composer require typo3/cms-recycler:^12.4.37 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-workspaces, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-workspaces to 12.4.37 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2fhw-2j7m-mr4m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-2fhw-2j7m-mr4m can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2fhw-2j7m-mr4m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2fhw-2j7m-mr4m in your dependencies?
O3 Security finds GHSA-2fhw-2j7m-mr4m across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.