Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
LOW severity

GHSA-6r58-4xgr-gm6m

LOW

GHSA-6r58-4xgr-gm6m is a low-severity (CVSS 2.7) vulnerability in silverstripe/framework. O3 Security confirms whether GHSA-6r58-4xgr-gm6m is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

SilverStripe Priviledge escalation through cache pollution

Also known asCVE-2019-12617
Published
Nov 12, 2019
Updated
Nov 30, 2024
Affected
2 pkgs
Patched
2 / 2
Exploits
None indexed
Exploitation data as of Nov 30, 2024 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected
🐘silverstripe/framework🐘silverstripe/framework

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

In SilverStripe through 4.3.3, there is access escalation for CMS users with limited access through permission cache pollution.

Affected Packages

2 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistsilverstripe/framework4.4.0&&< 4.4.44.4.4
🐘Packagistsilverstripe/framework4.3.0&&< 4.3.54.3.5

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for silverstripe/framework. 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.

  2. Fix

    Update silverstripe/framework to 4.4.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6r58-4xgr-gm6m is resolved across your whole dependency graph.

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

  4. How O3 protects you

    O3 pinpoints whether GHSA-6r58-4xgr-gm6m 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-6r58-4xgr-gm6m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In SilverStripe through 4.3.3, there is access escalation for CMS users with limited access through permission cache pollution.
O3 Security · Impact-Aware SCA

Is GHSA-6r58-4xgr-gm6m in your dependencies?

O3 detects GHSA-6r58-4xgr-gm6m across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

GHSA-6r58-4xgr-gm6m: SilverStripe… | O3 Security