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).
Published May 27, 2024
Affected packages
silverstripe/framework
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.1.19-rc1, < 3.1.20
- Fixed in
- 3.1.20
- Check
composer show silverstripe/framework
silverstripe/framework
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.2.4-rc1, < 3.2.5
- Fixed in
- 3.2.5
- Check
composer show silverstripe/framework
silverstripe/framework
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.3.2-rc1, < 3.3.3
- Fixed in
- 3.3.3
- Check
composer show silverstripe/framework
silverstripe/framework
- Ecosystem
- Composer (PHP)
- Affected
- >= 3.4.0-rc1, < 3.4.1
- Fixed in
- 3.4.1
- Check
composer show silverstripe/framework
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
References
- https://github.com/silverstripe/silverstripe-framework/commit/2b30ade44d333a4da4d13b31ffa28d0a34597442
- https://github.com/silverstripe/silverstripe-framework/commit/6606d986634f5b5dec16462acaa8d9a513c29fec
- https://github.com/silverstripe/silverstripe-framework/commit/6d41db77fa78f473db7bcff389456c980ef4e412
- https://github.com/silverstripe/silverstripe-framework/commit/782c18fd13b9fb92707d0ea3b231023204928297
- https://github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2016-011-1.yaml
- https://www.silverstripe.org/download/security-releases/ss-2016-011
- https://github.com/advisories/GHSA-p5h2-vr99-xm99
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-88987
Silverstripe Framework: XSS via XHTML data URI
medium5.4Nov 16, 2026CVE-2026-88988
Silverstripe Framework: XSS via SVG data URI
medium5.4Nov 16, 2026CVE-2026-88989
Silverstripe Framework: Auth bypass GridFieldDetailForm
medium4.3Nov 16, 2026CVE-2026-91112
Silverstripe Framework: CMS_ACCESS_SecurityAdmin privilege escalation
medium6.8Nov 16, 2026CVE-2026-91113
Silverstripe Framework: User-controlled ClassName allows unauthorized record type change
medium4.3Nov 16, 2026CVE-2026-91115
Silverstripe Framework: RCE via i18nTextCollectorTask writer parameter
high8.8Nov 16, 2026
