CVE-2025-9824
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-09-03

Last updated on: 2025-09-04

Assigner: Mautic

Description
ImpactThe attacker can validate if a user exists by checking the time login returns. This timing difference can be used to enumerate valid usernames, after which an attacker could attempt brute force attacks. PatchesThis vulnerability has been patched, implementing a timing-safe form login authenticator that ensures consistent response times regardless of whether a user exists or not. Technical DetailsThe vulnerability was caused by different response times when: * A valid username was provided (password hashing occurred) * An invalid username was provided (no password hashing occurred) The fix introduces a TimingSafeFormLoginAuthenticator that performs a dummy password hash verification even for non-existent users, ensuring consistent timing. WorkaroundsNo workarounds are available. Users should upgrade to the patched version. References * https://owasp.org/www-project-web-security-testing-guide/latest/4-Web_Application_Security_Testing/03-Identity_Management_Testing/04-Testing_for_Account_Enumeration_and_Guessable_User_Account
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-09-03
Last Modified
2025-09-04
Generated
2026-06-16
AI Q&A
2025-09-03
EPSS Evaluated
2026-06-15
NVD
CVE-2025-9824
EUVD
EUVD-2025-26524
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
mautic mautic *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-204 The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

This vulnerability is a user enumeration issue caused by timing differences in login responses. When a valid username is submitted, the system performs password hashing, which takes longer, whereas for invalid usernames, no hashing occurs, resulting in faster responses. Attackers can measure these timing differences to confirm whether a username exists, enabling them to enumerate valid users and potentially launch brute force attacks. [1]

Impact Analysis

The vulnerability allows attackers to determine valid usernames by analyzing response times during login attempts. Once valid usernames are identified, attackers can attempt brute force attacks to compromise accounts. This can lead to denial of service or unauthorized access attempts, impacting system availability and security. [1]

Detection Guidance

This vulnerability can be detected by measuring the response times of login attempts with different usernames. Specifically, an attacker can send login requests with various usernames and observe timing differences: valid usernames cause longer response times due to password hashing, while invalid usernames respond faster. To detect this on your system, you can use tools like curl or automated scripts to send login requests and measure response times. For example, using curl with time measurement: curl -w "%{time_total}\n" -o /dev/null -s -X POST -d 'username=someuser&password=somepass' https://your-login-url. Repeating this with different usernames and comparing response times can reveal timing discrepancies indicative of the vulnerability. [1]

Mitigation Strategies

The immediate step to mitigate this vulnerability is to upgrade your Mautic installation to a patched version that includes the TimingSafeFormLoginAuthenticator fix. Specifically, upgrade to versions 4.4.17, 5.2.8, or 6.0.5 or later. There are no workarounds available, so applying the official patch is necessary to ensure consistent response times and prevent username enumeration via timing attacks. [1]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-9824. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart