Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
Silverstripe framework versions from 3.4.0-rc1 before 3.4.6 and from 3.5.0-rc1 before 3.5.4 are affected. The login form's brute force lockout messages differed between existing and non-existent users, so an attacker can tell which accounts exist in the member table. The source gives few details on the attack conditions. Upgrade to 3.4.6 or 3.5.4, where login attempt logging and lockout behave the same for both kinds of user.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 5.3 | Medium | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N | GitHub Advisory Database |
- CISA KEV Not listed.
- EPSS No score.
Timeline
- 31 Oct 2026, 14:28 UTC First seen by agentprime
- 31 Oct 2026, 14:28 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-g84q-cq55-xwgp
- OSV: GHSA-g84q-cq55-xwgp
- github.com/silverstripe/silverstripe-framework/commit/f71efb5063c57d823dd130b9bfd018f6ef903d49
- github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2017-002-1.yaml
- github.com/silverstripe/silverstripe-framework
- www.silverstripe.org/download/security-releases/ss-2017-002