Summary
Mautic Vulnerable to User Enumeration via Response Timing
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
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.
CVE-2025-9824 has a CVSS score of 5.9 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.4.17, 5.2.8, 6.0.5); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
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.
Frequently Asked Questions
- What is CVE-2025-9824? CVE-2025-9824 is a medium-severity security vulnerability in mautic/core (composer), affecting versions >= 4.4.0, < 4.4.17. It is fixed in 4.4.17, 5.2.8, 6.0.5.
- How severe is CVE-2025-9824? CVE-2025-9824 has a CVSS score of 5.9 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of mautic/core are affected by CVE-2025-9824? mautic/core (composer) versions >= 4.4.0, < 4.4.17 is affected.
- Is there a fix for CVE-2025-9824? Yes. CVE-2025-9824 is fixed in 4.4.17, 5.2.8, 6.0.5. Upgrade to this version or later.
- Is CVE-2025-9824 exploitable, and should I be worried? Whether CVE-2025-9824 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-9824 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-9824?
- Upgrade
mautic/coreto 4.4.17 or later - Upgrade
mautic/coreto 5.2.8 or later - Upgrade
mautic/coreto 6.0.5 or later
- Upgrade