User ID Enumeration Vulnerability in silverstripe/framework

silverstripe/framework Updated 02 Oct 2025

Summary

27/05/2024
MODERATE
Yes i
Moderate
5.3

GHSA-crr3-h4m8-7f56: silverstripe/framework vulnerable to member disclosure in login form. Affects silverstripe/framework across 2 version ranges.

>= 4.0.0-rc1, < 4.0.4 >= 4.1.0-rc1, < 4.1.1

Fixed in 4.0.4 or 4.1.1, depending on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

silverstripe/framework is an open-source PHP framework used for building websites and web applications. It provides a range of features and functionalities to developers, including a login form for user authentication. However, the framework is vulnerable to a user ID enumeration vulnerability in its login form.

Vulnerability Detail

The vulnerability allows an attacker to infer or confirm user details that exist in the member table. By exploiting the brute force error messages, the attacker can differentiate between non-existent users and existing users. Non-existent users will never receive a locked out message, while existing users will receive a locked out message. This vulnerability can lead to the disclosure of sensitive user information and potentially facilitate unauthorized access to user accounts.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 4.0.0-rc1, < 4.0.4 4.0.4
    composer require silverstripe/framework:4.0.4
  • >= 4.1.0-rc1, < 4.1.1 4.1.1
    composer require silverstripe/framework:4.1.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no specific workaround mentioned for this vulnerability. It is recommended to update to the fixed versions of the silverstripe/framework package.

Conclusion

The user ID enumeration vulnerability in silverstripe/framework's login form can lead to the disclosure of sensitive user information and potential unauthorized access to user accounts. It is crucial to update to the fixed versions of the package (4.0.4 or 4.1.1) to ensure the security of your application. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for silverstripe/framework →

Share this vulnerability

FAQ

The vulnerability allows an attacker to infer or confirm the existence of user accounts in the member table, potentially leading to unauthorized access to user accounts.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your application is affected by this vulnerability. It analyzes your composer.lock file and provides real-time alerts for open-source vulnerabilities.

There are no known exploits for this vulnerability at the moment. However, it is important to patch your application to prevent any potential attacks.

Yes, the vulnerability has been fixed in the following versions of the silverstripe/framework package: 4.0.4 and 4.1.1.

If you have an older version of the silverstripe/framework package, it is recommended to update to one of the fixed versions (4.0.4 or 4.1.1) to mitigate the vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for silverstripe/framework.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 4.0.0-rc1, < 4.0.4 4.0.4
    composer require silverstripe/framework:4.0.4
  • >= 4.1.0-rc1, < 4.1.1 4.1.1
    composer require silverstripe/framework:4.1.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback