PT-2025-36604 · Packagist · Mautic/Core

Published 2025-09-03 · Updated 2025-09-03

OSV

CVSS v3.1

5.9

Medium

Base vector

AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

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

Fix

Weakness Enumeration

CWE-204

Related Identifiers

GHSA-3GGV-QWCP-J6XG

Affected Products

Mautic/Core

References · 6

• https://osv.dev/vulnerability/GHSA-3ggv-qwcp-j6xg · Vendor Advisory
• https://nvd.nist.gov/vuln/detail/CVE-2025-9824 · Security Note
• https://github.com/mautic/mautic/security/advisories/GHSA-3ggv-qwcp-j6xg · Note
• https://github.com/mautic/mautic · Note
• https://github.com/mautic/mautic/commit/6bc4f5f1aabb13df12714ad0ea9fc281cbb867c6 · Note
• https://github.com/mautic/mautic/commit/b4264c717ce31fbafafcefc04b02ecb9fb911e62 · Note