Skip to content
Fencer Intel
medium 4.3

GHSA-p5h2-vr99-xm99 json

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

published 2y ago modified last yr.

cvss
4.3
version 3.1, GitHub
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

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.

Patch / fix

  • packagist silverstripe/framework 3.1.20, 3.2.5, 3.3.3, 3.4.1

Is GHSA-p5h2-vr99-xm99 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CVSS scores

assigned by version score vector
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Affected packages

ecosystem package affected fixed in
packagist silverstripe/framework
>=3.1.19-rc1, <3.1.20
>=3.2.4-rc1, <3.2.5
>=3.3.2-rc1, <3.3.3
>=3.4.0-rc1, <3.4.1
3.1.20
3.2.5
3.3.3
3.4.1

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.