GHSA-p5h2-vr99-xm99 is a medium-severity (CVSS 4.3) vulnerability in silverstripe/framework. A fix is available for silverstripe/framework — see the affected versions and patch details below.
silverstripe/framework ChangePasswordForm does not check `Member::canLogIn()`
Real-World Exposure
silverstripe/framework🐘silverstripe/framework🐘silverstripe/framework🐘silverstripe/frameworkReal-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
After performing a password reset, ChangePasswordForm::doChangePassword() logs in the user without checking Member::canLogIn(). This presents an issue for sites that are using the extension point in that method to deny access to users (for example members that have not been “approved”, or members that have had their access revoked temporarily). It looks like Member::canLogIn() was originally designed to only be used for checking whether the user is locked out (due to too many incorrect login attempts) but has been opened up to other uses.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | silverstripe/framework | ≥ 3.1.19-rc1&&< 3.1.20 | 3.1.20composer require silverstripe/framework:^3.1.20 |
| 🐘Packagist | silverstripe/framework | ≥ 3.2.4-rc1&&< 3.2.5 | 3.2.5composer require silverstripe/framework:^3.2.5 |
| 🐘Packagist | silverstripe/framework | ≥ 3.3.2-rc1&&< 3.3.3 | 3.3.3composer require silverstripe/framework:^3.3.3 |
| 🐘Packagist | silverstripe/framework | ≥ 3.4.0-rc1&&< 3.4.1 | 3.4.1composer require silverstripe/framework:^3.4.1 |
Detection & mitigation playbook
Open-source dependencyDetect
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.
Fix
Update silverstripe/framework to 3.1.20 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p5h2-vr99-xm99 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-p5h2-vr99-xm99 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-p5h2-vr99-xm99. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-p5h2-vr99-xm99 in your dependencies?
O3 Security finds GHSA-p5h2-vr99-xm99 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.