User ID Enumeration Vulnerability in silverstripe/framework

silverstripe/framework Updated 02 Oct 2025

Summary

27/05/2024
MODERATE
Yes i
Moderate
5.3

GHSA-g84q-cq55-xwgp: silverstripe/framework member disclosure in login form. Affects silverstripe/framework across 2 version ranges.

>= 3.4.0-rc1, < 3.4.6 >= 3.5.0-rc1, < 3.5.4

Fixed in 3.4.6 or 3.5.4, 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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

silverstripe/framework is a PHP framework used for building websites and web applications. It provides a range of features and functionalities to developers, including user authentication and login functionality. However, a vulnerability has been discovered in the login form of the framework, which allows for user ID enumeration.

Vulnerability Detail

The vulnerability in silverstripe/framework's login form allows an attacker to infer or confirm the existence of user details in the member table. By exploiting this vulnerability, an attacker can determine whether a user exists in the system or not. This can be done by analyzing the brute force error messages returned by the login form. Non-existent users will never receive a locked out message, while existing users will receive a locked out message. This information disclosure can aid attackers in their attempts to gain unauthorized access to user accounts.

How To Fix

Fixed versions by release line

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

  • >= 3.4.0-rc1, < 3.4.6 3.4.6
    composer require silverstripe/framework:3.4.6
  • >= 3.5.0-rc1, < 3.5.4 3.5.4
    composer require silverstripe/framework:3.5.4

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 available for this vulnerability. It is recommended to update the silverstripe/framework package to the fixed versions mentioned above.

Conclusion

The user ID enumeration vulnerability in silverstripe/framework's login form can lead to unauthorized access to user accounts. It is crucial to update the silverstripe/framework package to the fixed versions (3.4.6 or 3.5.4) to mitigate this vulnerability. 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 attackers to determine the existence of user details in the member table, which can aid in unauthorized access to user accounts.

You can use the Vulert Playground at Vulert Scanner to check if your application is affected by this vulnerability. Simply upload your composer.lock file and the playground will analyze it for vulnerabilities.

There are no known exploits for this vulnerability at the moment. However, it is important to update to the fixed versions to prevent any potential attacks.

No, the recommended mitigation is to update the silverstripe/framework package to the fixed versions.

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.

  • >= 3.4.0-rc1, < 3.4.6 3.4.6
    composer require silverstripe/framework:3.4.6
  • >= 3.5.0-rc1, < 3.5.4 3.5.4
    composer require silverstripe/framework:3.5.4

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