CVE-2025-9824: Mautic Vulnerable to User Enumeration via Response Timing
Impact The 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. Patches This vulnerability has been patched, implementing a timing-safe form login authenticator that ensures consistent response times regardless of whether a user exists or not.
Published Sep 3, 2025
Affected packages
mautic/core
- Ecosystem
- Composer (PHP)
- Affected
- >= 4.4.0, < 4.4.17
- Fixed in
- 4.4.17
- Check
composer show mautic/core
mautic/core
- Ecosystem
- Composer (PHP)
- Affected
- >= 5.0.0-alpha, < 5.2.8
- Fixed in
- 5.2.8
- Check
composer show mautic/core
mautic/core
- Ecosystem
- Composer (PHP)
- Affected
- >= 6.0.0-alpha, < 6.0.5
- Fixed in
- 6.0.5
- Check
composer show mautic/core
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
The 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.
Patches
This 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 Details
The 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.
Workarounds
No 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
- https://github.com/mautic/mautic-security/pull/146
Credited to Vautia, kuzmany.
References
- https://github.com/mautic/mautic/security/advisories/GHSA-3ggv-qwcp-j6xg
- https://nvd.nist.gov/vuln/detail/CVE-2025-9824
- https://github.com/mautic/mautic/commit/6bc4f5f1aabb13df12714ad0ea9fc281cbb867c6
- https://github.com/mautic/mautic/commit/b4264c717ce31fbafafcefc04b02ecb9fb911e62
- https://github.com/advisories/GHSA-3ggv-qwcp-j6xg
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-4776
Mautic has SQL Injection in API Contact Filtering
high7.1No fixJul 2, 2026CVE-2026-9557
Mautic Focus component Vulnerable to SSRF
medium6.4No fixJul 2, 2026CVE-2026-9558
Mautic has Server-Side Template Injection (SSTI) in Theme Templates
critical9.9No fixJul 2, 2026CVE-2026-9559
Mautic vulnerable to Path Traversal via Campaign Import
critical9.9Jul 2, 2026CVE-2026-9808
Mautic has an Authorization Bypass in API v2 Endpoints
high7.1Jul 2, 2026CVE-2026-9809
Mautic has Stored Cross-Site Scripting (XSS) in Projects Component
high7.6Jul 2, 2026
