CVE-2025-9824
User Enumeration via Response Timing
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
INFO
Published Date :
Sept. 3, 2025, 3:15 p.m.
Last Modified :
Oct. 19, 2026, 5:10 p.m.
Remotely Exploit :
Yes !
Source :
[email protected]
CVSS Scores
| Score | Version | Severity | Vector | Exploitability Score | Impact Score | Source |
|---|---|---|---|---|---|---|
| CVSS | 134c704f-9b21-4f2e-91b3-4a467353bcc0 | |||||
| CVSS 3.1 | MEDIUM | [email protected] | ||||
| CVSS 3.1 | MEDIUM | MITRE-CVE |
Solution
- Apply the security patch for the timing-safe form login authenticator.
- Upgrade to the patched version of the software.
References to Advisories, Solutions, and Tools
Here, you will find a curated list of external links that provide in-depth
information, practical solutions, and valuable tools related to
CVE-2025-9824.
| URL | Resource |
|---|---|
| https://github.com/mautic/mautic/security/advisories/GHSA-3ggv-qwcp-j6xg |
CWE - Common Weakness Enumeration
While CVE identifies
specific instances of vulnerabilities, CWE categorizes the common flaws or
weaknesses that can lead to vulnerabilities. CVE-2025-9824 is
associated with the following CWEs:
Common Attack Pattern Enumeration and Classification (CAPEC)
Common Attack Pattern Enumeration and Classification
(CAPEC)
stores attack patterns, which are descriptions of the common attributes and
approaches employed by adversaries to exploit the CVE-2025-9824
weaknesses.
We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).
Results are limited to the first 15 repositories due to potential performance issues.
The following list is the news that have been mention
CVE-2025-9824 vulnerability anywhere in the article.
The following table lists the changes that have been made to the
CVE-2025-9824 vulnerability over time.
Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.
-
CVE Translated by [email protected]
Oct. 19, 2026
Action Type Old Value New Value Added Translation Title: Mautic, Description: Impacto El atacante puede validar si un usuario existe comprobando el tiempo que devuelve el inicio de sesión. Esta diferencia de tiempo puede ser utilizada para enumerar nombres de usuario válidos, después de lo cual un atacante podría intentar ataques de fuerza bruta. Parches Esta vulnerabilidad ha sido parcheada, implementando un autenticador de inicio de sesión de formulario seguro contra ataques de temporización que asegura tiempos de respuesta consistentes independientemente de si un usuario existe o no. Detalles Técnicos La vulnerabilidad fue causada por diferentes tiempos de respuesta cuando: * Se proporcionó un nombre de usuario válido (se realizó el hash de la contraseña) * Se proporcionó un nombre de usuario inválido (no se realizó el hash de la contraseña) La solución introduce un TimingSafeFormLoginAuthenticator que realiza una verificación de hash de contraseña ficticia incluso para usuarios inexistentes, asegurando una temporización consistente. Soluciones provisionales No hay soluciones provisionales disponibles. Los usuarios deben actualizar a la versión parcheada. Referencias * 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 -
CVE Modified by [email protected]
Jun. 17, 2026
Action Type Old Value New Value Added Affected [{'repo': 'https://github.com/mautic/mautic', 'vendor': 'Mautic', 'product': 'Mautic', 'versions': [{'status': 'affected', 'version': '>= 4.4.0', 'lessThan': '< 4.4.17', 'versionType': 'semver'}, {'status': 'affected', 'version': '>= 5.0.0-alpha', 'lessThan': '< 5.2.8', 'versionType': 'semver'}, {'status': 'affected', 'version': '>= 6.0.0-alpha', 'lessThan': '< 6.0.5', 'versionType': 'semver'}], 'packageName': 'mautic/core', 'collectionURL': 'https://packagist.org', 'defaultStatus': 'unaffected'}] -
CVE Modified by 134c704f-9b21-4f2e-91b3-4a467353bcc0
Jun. 17, 2026
Action Type Old Value New Value Added SSVC {'id': 'CVE-2025-9824', 'role': 'CISA Coordinator', 'options': [{'exploitation': 'none'}, {'automatable': 'no'}, {'technicalImpact': 'partial'}], 'version': '2.0.3', 'timestamp': '2025-09-03T14:45:46.949698Z'} -
New CVE Received by [email protected]
Sep. 03, 2025
Action Type Old Value New Value Added 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 Added CVSS V3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H Added CWE CWE-204 Added Reference https://github.com/mautic/mautic/security/advisories/GHSA-3ggv-qwcp-j6xg