Medium

Mautic Vulnerable to User Enumeration via Response Timing

  • Disclosed: 03.09.2025
  • Updated: 11.10.2026 10:22

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

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package mautic/core >= 4.4.0, < 4.4.17, >= 5.0.0-alpha, < 5.2.8, >= 6.0.0-alpha, < 6.0.5 4.4.17, 5.2.8, 6.0.5

References

CVSS score 5.9/10
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
Weakness (CWE)
CWE-204
Platform
Composer
Package
mautic/core
Disclosed
03.09.2025
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-3ggv-qwcp-j6xg - CC BY 4.0

Vulnerability history: mautic/core

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (57) in the archive
Total entries
57
First → latest
01.2021 07.2026
Without a fix
1
Exploited in attacks
0

Severity breakdown

  • Critical 9
  • High 17
  • Medium 29
  • Low 2

Disclosures per year

  1. 2021: 16
  2. 2022: 7
  3. 2023: 0
  4. 2024: 13
  5. 2025: 13
  6. 2026: 8
Severity:
  1. High · 7.6 CVE-2026-9809 >= 7.0.0, < 7.1.2 7.1.2
  2. High · 7.1 CVE-2026-9808 >= 7.0.0, < 7.1.2 7.1.2
  3. Critical · 9.9 CVE-2026-9559 >= 7.0.0, < 7.1.2 7.1.2
  4. Critical · 9.9 CVE-2026-9558 >= 1.3.0, >= 5.0.0, < 5.2.11, >= 6.0.0, < 6.0.9, >= 7.0.0, < 7.1.2 5.2.11, 6.0.9, 7.1.2
  5. High · 7.1 CVE-2026-4776 >= 2.6.0, <= 4.4.13, >= 5.0.0, < 5.2.11, >= 6.0.0, < 6.0.9, >= 7.0.0, < 7.1.2 5.2.11, 6.0.9, 7.1.2
  6. High · 7.6 CVE-2026-3105 >= 2.10.0, < 5.2.10, >= 6.0.0-alpha, < 6.0.8, >= 7.0.0-alpha, < 7.0.1 5.2.10, 6.0.8, 7.0.1
  7. Critical CVE-2025-13828 >= 4.0.0, < 4.4.18, >= 5.0.0, < 5.2.9, >= 6.0.0, < 6.0.7 4.4.18, 5.2.9, 6.0.7
  8. Mautic Vulnerable to User Enumeration via Response Timing this entry
    Medium · 5.9 CVE-2025-9824 >= 4.4.0, < 4.4.17, >= 5.0.0-alpha, < 5.2.8, >= 6.0.0-alpha, < 6.0.5 4.4.17, 5.2.8, 6.0.5
  9. High · 7.7 CVE-2024-47053 >= 1.0.1, < 5.2.3 5.2.3
  10. Critical · 9.1 CVE-2024-47051 < 5.2.3 5.2.3
  11. High · 7.0 CVE-2022-25768 >= 1.1.3, < 4.4.13, >= 5.0.0-alpha, < 5.1.1 4.4.13, 5.1.1
  12. Critical · 9.6 CVE-2020-35125 < 2.16.5, >= 3.0.0, < 3.2.4 2.16.5, 3.2.4
  13. High · 8.3 CVE-2022-25776 >= 1.0.2, < 4.4.12, >= 5.0.0-alpha, < 5.0.4 4.4.12, 5.0.4
  14. High · 8.1 CVE-2021-27916 >= 3.3.0, < 4.4.12, >= 5.0.0-alpha, < 5.0.4 4.4.12, 5.0.4
  15. High · 7.6 CVE-2021-27915 >= 1.0.0-beta2, < 4.4.12 4.4.12
  16. Critical · 9.0 CVE-2020-35129 < 3.2.4 3.2.4
  17. Critical · 9.0 CVE-2020-35128 >= 3.2.0, < 3.2.4, >= 2.0.0, < 2.16.5 3.2.4, 2.16.5
  18. High · 7.5 CVE-2017-1000046 < 2.1.1 2.1.1
  19. High · 8.8 CVE-2017-8874 = 1.4.1 no fix
  20. High · 8.2 CVE-2021-27910 < 3.3.4, >= 4.0.0-alpha1, < 4.0.0 3.3.4, 4.0.0
  21. High · 8.3 CVE-2021-27911 < 3.3.4, >= 4.0.0-alpha1, < 4.0.0 3.3.4, 4.0.0
  22. High · 7.1 CVE-2021-27912 < 3.3.4, >= 4.0.0-alpha1, < 4.0.0 3.3.4, 4.0.0
  23. High CVE-2021-3142 >= 3.0.0, < 3.2.4, >= 2.0.0, < 2.16.5 3.2.4, 2.16.5
  24. High · 8.1 CVE-2017-1000489 >= 2.0.0, < 2.12.0 2.12.0
  25. Critical CVE-2020-35124 >= 3.0.0, < 3.2.4, >= 2.0.0, < 2.16.5 3.2.4, 2.16.5

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.