NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
HIGH severity

Silverstripe CMS information disclosureGHSA-gm5x-hpmw-xpxg

HIGHFix: silverstripe/silverstripe-framework@91d30db

GHSA-gm5x-hpmw-xpxg is a high-severity (CVSS 7.5) vulnerability in silverstripe/cms. A fix is available for silverstripe/cms — see the affected versions and patch details below.

Also known asBIT-silverstripe-2020-6164CVE-2020-6164
Published
Updated
Affected
3 pkgs
Patched
2 / 3
Exploits
None indexed
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs79th percentile — riskier than 79% of all scored CVEsHighest risk
0.20%0.90%1.60%2.30%0.7%1.8%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected
🐘silverstripe/cms🐘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.5.0, a specific URL path configured by default through the silverstripe/framework module can be used to disclose the fact that a domain is hosting a Silverstripe application. There is no disclosure of the specific version. The functionality on this URL path is limited to execution in a CLI context, and is not known to present a vulnerability through web-based access. As a side-effect, this preconfigured path also blocks the creation of other resources on this path (e.g. a page).

Affected Packages

3 total 2 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistsilverstripe/cmsall versionsNo fix
🐘Packagistsilverstripe/framework≥ 4.0.0&&< 4.4.74.4.7composer require silverstripe/framework:^4.4.7
🐘Packagistsilverstripe/framework≥ 4.5.0&&< 4.5.44.5.4composer require silverstripe/framework:^4.5.4

Affected Products

1 product · 3 configurations
Application
silverstripesilverstripe
≥ 4.5.0 && ≤ 3.0.0
range

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/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    A fix is available for GHSA-gm5x-hpmw-xpxg; check the affected-versions list above or the advisory for the patched release of silverstripe/cms, then make sure no transitive dependency still pins the vulnerable range.

  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.

Frequently Asked Questions

In SilverStripe through 4.5.0, a specific URL path configured by default through the silverstripe/framework module can be used to disclose the fact that a domain is hosting a Silverstripe application. There is no disclosure of the specific version. The functionality on this URL path is limited to execution in a CLI context, and is not known to present a vulnerability through web-based access. As a side-effect, this preconfigured path also blocks the creation of other resources on this path (e.g. a page).
O3 Security · Impact-Aware SCA

Is GHSA-gm5x-hpmw-xpxg in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
Silverstripe CMS information disclosure (High 7.5)