Skip to content

Mautic Vulnerable to User Enumeration via Response Timing

Moderate severity GitHub Reviewed Published Sep 3, 2025 in mautic/mautic • Updated Sep 3, 2025

Package

composer mautic/core (Composer)

Affected versions

>= 4.4.0, < 4.4.17
>= 5.0.0-alpha, < 5.2.8
>= 6.0.0-alpha, < 6.0.5

Patched versions

4.4.17
5.2.8
6.0.5

Description

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

References

@kuzmany kuzmany published to mautic/mautic Sep 3, 2025
Published by the National Vulnerability Database Sep 3, 2025
Published to the GitHub Advisory Database Sep 3, 2025
Reviewed Sep 3, 2025
Last updated Sep 3, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(11th percentile)

Weaknesses

Observable Response Discrepancy

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. Learn more on MITRE.

CVE ID

CVE-2025-9824

GHSA ID

GHSA-3ggv-qwcp-j6xg

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.