GHSA-rf5m-h8q9-9w6q is a low-severity (CVSS 3.1) CWE-863 vulnerability in typo3/cms-backend. A fix is available for typo3/cms-backend — see the affected versions and patch details below.
Information Disclosure in TYPO3 Page Tree
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-rf5m-h8q9-9w6q.
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.
How urgent is this, really
GHSA-rf5m-h8q9-9w6q plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
typo3/cms-backend🐘typo3/cms-backend🐘typo3/cms-backend🐘typo3/cms-backendReal-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
Problem
Backend users could see items in the backend page tree without having access if the mounts pointed to pages restricted for their user/group, or if no mounts were configured but the pages allowed access to "everybody." However, affected users could not manipulate these pages.
Solution
Update to TYPO3 versions 10.4.46 ELTS, 11.5.40 LTS, 12.4.21 LTS, 13.3.1 that fix the problem described.
Credits
Thanks to Peter Schuler who reported this issue and to TYPO3 core & security team member Oliver Hader who fixed the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-backend | ≥ 13.0.0&&< 13.3.1 | 13.3.1composer require typo3/cms-backend:^13.3.1 |
| 🐘Packagist | typo3/cms-backend | ≥ 12.0.0&&< 12.4.21 | 12.4.21composer require typo3/cms-backend:^12.4.21 |
| 🐘Packagist | typo3/cms-backend | ≥ 11.0.0&&< 11.5.40 | 11.5.40composer require typo3/cms-backend:^11.5.40 |
| 🐘Packagist | typo3/cms-backend | ≥ 10.0.0&&< 10.4.46 | 10.4.46composer require typo3/cms-backend:^10.4.46 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-backend, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-backend to 13.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rf5m-h8q9-9w6q 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-rf5m-h8q9-9w6q can be triaged on real exposure rather than presence alone.
Tailored to GHSA-rf5m-h8q9-9w6q. 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-rf5m-h8q9-9w6q in your dependencies?
O3 Security finds GHSA-rf5m-h8q9-9w6q across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.