User Enumeration Vulnerability in Silverstripe Framework: Timing Attack on Login and Password Reset Forms

silverstripe/framework Updated 02 Oct 2025

Summary

10/04/2025
MODERATE
Yes i
Moderate
5.3

GHSA-256q-hx8w-xcqx: Silverstripe Framework user enumeration via timing attack on login and password reset forms. Affects silverstripe/framework versions >= 4.0.0, < 5.3.23. Fixed in 5.3.23. 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 Penetration testing for web, API and mobile 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 content management system (CMS) and framework for building web applications. It provides a robust set of tools for developers to create dynamic websites with ease. However, it has been identified that versions 4.0.0 and above are vulnerable to a user enumeration issue, which can be exploited through timing attacks on the login and password reset forms.

Vulnerability Detail

The vulnerability allows attackers to enumerate valid usernames by measuring the response time of the login and password reset forms. If an attacker submits a request with an invalid username, the response time will differ from that of a valid username, thus revealing whether the username exists in the system. This issue was initially disclosed in a security release for CMS 3 but was not addressed in CMS 4 and later versions. The potential ramifications include unauthorized access attempts and targeted attacks on valid user accounts.

How To Fix

Minimum fixed version

5.3.23

This is the first release that contains the fix.

composer require silverstripe/framework:5.3.23

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, you can implement rate limiting on login attempts and password reset requests to reduce the effectiveness of timing attacks. Additionally, consider adding a generic error message that does not disclose whether the username exists or not.

Conclusion

The Silverstripe Framework has a vulnerability that allows user enumeration through timing attacks on login and password reset forms. It is crucial to update to the latest patched version to mitigate this risk. Implementing workarounds can provide temporary relief, but updating is the most effective solution.

See every vulnerability recorded for silverstripe/framework →

Share this vulnerability

FAQ

A timing attack is a type of side-channel attack where an attacker attempts to compromise a system by analyzing the time it takes to execute cryptographic algorithms or respond to requests.

You can check if your application is affected by using Vulert, which monitors and alerts for open-source vulnerabilities in real-time. You can use the Vulert playground at Vulert Scanner without any signup.

User enumeration can lead to targeted attacks, where an attacker can focus on valid usernames to attempt unauthorized access, potentially compromising user accounts.

While updating is the best solution, you can implement rate limiting and generic error messages as workarounds to reduce the risk of exploitation.

The CVSS score of this vulnerability is 5.3, indicating a moderate level of severity.

Related vulnerabilities

Recent vulnerabilities recorded for silverstripe/framework.

How To Fix

Minimum fixed version

5.3.23

This is the first release that contains the fix.

composer require silverstripe/framework:5.3.23

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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