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

GHSA-256q-hx8w-xcqx silverstripe/framework

MEDIUMFix: silverstripe/silverstripe-framework#11681

GHSA-256q-hx8w-xcqx is a medium-severity (CVSS 5.3) vulnerability in silverstripe/framework. A fix is available for silverstripe/framework — see the affected versions and patch details below.

Silverstripe Framework user enumeration via timing attack on login and password reset forms

Published
Apr 10, 2025
Updated
Apr 10, 2025
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Apr 10, 2025 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected
🐘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

Impact

User enumeration is possible by performing a timing attack on the login or password reset pages with user credentials.

This was originally disclosed in https://www.silverstripe.org/download/security-releases/ss-2017-005/ for CMS 3 but was not patched in CMS 4+

References

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistsilverstripe/framework4.0.0&&< 5.3.235.3.23composer require silverstripe/framework:^5.3.23

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 5.3.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-256q-hx8w-xcqx 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-256q-hx8w-xcqx can be triaged on real exposure rather than presence alone.

Tailored to GHSA-256q-hx8w-xcqx. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact User enumeration is possible by performing a timing attack on the login or password reset pages with user credentials. This was originally disclosed in https://www.silverstripe.org/download/security-releases/ss-2017-005/ for CMS 3 but was not patched in CMS 4+ ### References - https://www.silverstripe.org/download/security-releases/ss-2017-005 - https://www.silverstripe.org/download/security-releases/ss-2025-001
O3 Security · Impact-Aware SCA

Is GHSA-256q-hx8w-xcqx in your dependencies?

O3 Security finds GHSA-256q-hx8w-xcqx across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

GHSA-256q-hx8w-xcqx: silverstripe/framework | O3 Security