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

GHSA-r85g-7jpv-8xrx silverstripe/framework

MEDIUMFix: silverstripe/silverstripe-framework@6b123fe

GHSA-r85g-7jpv-8xrx is a medium-severity (CVSS 6.1) vulnerability in silverstripe/framework. A fix is available for silverstripe/framework — see the affected versions and patch details below.

silverstripe/framework has Cross-site Scripting vulnerability in CMSSecurity BackURL

Published
May 27, 2024
Updated
Dec 2, 2024
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Dec 2, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

4 pkgs affected
🐘silverstripe/framework🐘silverstripe/framework🐘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 follow up to SS-2016-001 there is yet a minor unresolved fix to incorrectly encoded URL.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistsilverstripe/framework3.1.0-rc1&&< 3.1.213.1.21composer require silverstripe/framework:^3.1.21
🐘Packagistsilverstripe/framework3.2.0-rc1&&< 3.2.63.2.6composer require silverstripe/framework:^3.2.6
🐘Packagistsilverstripe/framework3.3.0-rc1&&< 3.3.43.3.4composer require silverstripe/framework:^3.3.4
🐘Packagistsilverstripe/framework3.4.0-rc1&&< 3.4.23.4.2composer require silverstripe/framework:^3.4.2

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

  2. Fix

    Update silverstripe/framework to 3.1.21 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-r85g-7jpv-8xrx 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-r85g-7jpv-8xrx can be triaged on real exposure rather than presence alone.

Tailored to GHSA-r85g-7jpv-8xrx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

In follow up to [SS-2016-001](https://www.silverstripe.org/download/security-releases/ss-2016-001/) there is yet a minor unresolved fix to incorrectly encoded URL.
O3 Security · Impact-Aware SCA

Is GHSA-r85g-7jpv-8xrx in your dependencies?

O3 Security finds GHSA-r85g-7jpv-8xrx across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-r85g-7jpv-8xrx: silverstripe/framework | O3 Security