GHSA-P5H2-VR99-XM99

silverstripe/framework ChangePasswordForm does not check Member::canLogIn()

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.

The application does not adequately verify the identity of a user, device, or process before granting access. Typical impact: unauthorized access to functions or data reserved for authenticated parties.

GHSA-P5H2-VR99-XM99 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (3.1.20, 3.2.5, 3.3.3, 3.4.1); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

1. What is GHSA-P5H2-VR99-XM99? GHSA-P5H2-VR99-XM99 is a medium-severity improper authentication vulnerability in silverstripe/framework (composer), affecting versions >= 3.1.19-rc1, < 3.1.20. It is fixed in 3.1.20, 3.2.5, 3.3.3, 3.4.1. The application does not adequately verify the identity of a user, device, or process before granting access.
2. How severe is GHSA-P5H2-VR99-XM99? GHSA-P5H2-VR99-XM99 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of silverstripe/framework are affected by GHSA-P5H2-VR99-XM99? silverstripe/framework (composer) versions >= 3.1.19-rc1, < 3.1.20 is affected.
4. Is there a fix for GHSA-P5H2-VR99-XM99? Yes. GHSA-P5H2-VR99-XM99 is fixed in 3.1.20, 3.2.5, 3.3.3, 3.4.1. Upgrade to this version or later.
5. Is GHSA-P5H2-VR99-XM99 exploitable, and should I be worried? Whether GHSA-P5H2-VR99-XM99 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-P5H2-VR99-XM99 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-P5H2-VR99-XM99?
   • Upgrade silverstripe/framework to 3.1.20 or later
   • Upgrade silverstripe/framework to 3.2.5 or later
   • Upgrade silverstripe/framework to 3.3.3 or later
   • Upgrade silverstripe/framework to 3.4.1 or later

Other vulnerabilities in silverstripe/framework