How severe is GHSA-rf5m-h8q9-9w6q?

GHSA-rf5m-h8q9-9w6q has a CVSS score of 3.1/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-rf5m-h8q9-9w6q?

GHSA-rf5m-h8q9-9w6q affects the following packages: typo3/cms-backend (Packagist), typo3/cms-backend (Packagist), typo3/cms-backend (Packagist), typo3/cms-backend (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-rf5m-h8q9-9w6q?

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.

How do I detect GHSA-rf5m-h8q9-9w6q in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-backend. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-rf5m-h8q9-9w6q if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-rf5m-h8q9-9w6q?

O3 pinpoints whether GHSA-rf5m-h8q9-9w6q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-rf5m-h8q9-9w6q actively exploited in the wild?

No public exploit code has been indexed for GHSA-rf5m-h8q9-9w6q yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-rf5m-h8q9-9w6q?

GHSA-rf5m-h8q9-9w6q has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 21th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-rf5m-h8q9-9w6q?

GHSA-rf5m-h8q9-9w6q is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-rf5m-h8q9-9w6q published, and has it been updated?

GHSA-rf5m-h8q9-9w6q was published on October 8, 2024 and was last updated on October 9, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

GHSA-rf5m-h8q9-9w6q: Information Disclosure in TYPO3 Page Tree…

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk21th percentile+0.03%

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.

Blast Radius

4 pkgs affected

🐘typo3/cms-backend🐘typo3/cms-backend🐘typo3/cms-backend🐘typo3/cms-backend

Real-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

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms-backend`	≥ 13.0.0&&< 13.3.1	13.3.1
🐘Packagist	`typo3/cms-backend`	≥ 12.0.0&&< 12.4.21	12.4.21
🐘Packagist	`typo3/cms-backend`	≥ 11.0.0&&< 11.5.40	11.5.40
🐘Packagist	`typo3/cms-backend`	≥ 10.0.0&&< 10.4.46	10.4.46

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-backend. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 pinpoints whether GHSA-rf5m-h8q9-9w6q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

### 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.

O3 Security · Impact-Aware SCA

Is GHSA-rf5m-h8q9-9w6q in your dependencies?

O3 detects GHSA-rf5m-h8q9-9w6q across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works

GHSA-rf5m-h8q9-9w6q