GHSA-crr3-h4m8-7f56
silverstripe/framework vulnerable to member disclosure in login form
GHSA-crr3-h4m8-7f56 is a medium vulnerability (CVSS 5.3) in silverstripe/framework, published May 27, 2024. No source lists public exploit code. Fixed in silverstripe/framework 4.0.4.
- Severity
- 5.3 MediumCVSS 3.1, GitHub Advisories
- Exploit chance
- UnscoredNo EPSS score yet
- Exploitation
- None knownNot on CISA’s or ENISA’s lists
- Fixed in
4.0.4silverstripe/framework +3 more
Description
There is a user ID enumeration vulnerability in our brute force error messages.
- Users that don't exist in will never get a locked out message
- Users that do exist, will get a locked out message
This means an attacker can infer or confirm user details that exist in the member table.
This issue has been resolved by ensuring that login attempt logging and lockout process works equivalently for non-existent users as it does for existant users.
This is a regression of SS-2017-002.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- None
What an attacker can affect
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Affected packages
| Package | Affected | Fixed |
|---|---|---|
silverstripe/frameworkPackagist | 4.0.0-rc1 up to 4.0.4 | 4.0.4 |
silverstripe/frameworkPackagist | 4.1.0-rc1 up to 4.1.1 | 4.1.1 |
silverstripe/frameworkPackagist | 4.0.0-rc1 up to 4.0.4, plus listed versions 4.0.04.0.0-rc24.0.0-rc34.0.14.0.1-rc14.0.24.0.3 | 4.0.4 |
silverstripe/frameworkPackagist | 4.1.0-rc1 up to 4.1.1, plus listed versions 4.1.04.1.0-rc2 | 4.1.1 |
What each source reports
GitHub Advisories Score used 5.3
silverstripe/framework vulnerable to member disclosure in login form
There is a user ID enumeration vulnerability in our brute force error messages.
- Users that don't exist in will never get a locked out message
- Users that do exist, will get a locked out message
This means an attacker can infer or confirm user details that exist in the member table.
This issue has been resolved by ensuring that login attempt logging and lockout process works equivalently for non-existent users as it does for existant users.
This is a regression of SS-2017-002.
- Record
GHSA-crr3-h4m8-7f56- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-200
- Updated
- 2026-11-02
OSV 5.3
silverstripe/framework vulnerable to member disclosure in login form
There is a user ID enumeration vulnerability in our brute force error messages.
- Users that don't exist in will never get a locked out message
- Users that do exist, will get a locked out message
This means an attacker can infer or confirm user details that exist in the member table.
This issue has been resolved by ensuring that login attempt logging and lockout process works equivalently for non-existent users as it does for existant users.
This is a regression of SS-2017-002.
- Record
GHSA-crr3-h4m8-7f56- CVSS 3.1
- 5.3 Medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N - Weakness
- CWE-200
- Updated
- 2026-11-02
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
References
github.com/silverstripe/silverstripe-framework/commit/5887201dd578a5b9779c33a182153d2ce973ab41
github.com/FriendsOfPHP/security-advisories/blob/master/silverstripe/framework/SS-2018-010-1.yaml
silverstripe.org/download/security-releases/ss-2018-010
github.com/advisories/GHSA-crr3-h4m8-7f56
github.com/silverstripe/silverstripe-framework