CVE-2025-9824
ImpactThe 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.
PatchesThis 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 DetailsThe vulnerability was caused by different response times when:
The fix introduces a TimingSafeFormLoginAuthenticator that performs a dummy password hash verification even for non-existent users, ensuring consistent timing.
Leer descripción completaMostrar menos
WorkaroundsNo 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
Detalles técnicos trazas, registros y código del informe original
* A valid username was provided (password hashing occurred) * An invalid username was provided (no password hashing occurred)
CVSS
- Versión: 3.1
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
- Puntuación base: 5.9
Probabilidad de explotación (EPSS)
- Probabilidad de explotación en los próximos 30 días: 0.28%
- Percentil entre todas las CVEs puntuadas: 19
- Fecha de la puntuación: 6/10/2026
EPSS (Exploit Prediction Scoring System, de FIRST) estima la probabilidad de que una vulnerabilidad sea explotada en 30 días. Complementa a CVSS (impacto) y a CISA KEV (explotación confirmada).
CWE
- CWE-204
Referencias
JSON original (NVD)
Mostrar
{
"id": "CVE-2025-9824",
"cveTags": [],
"metrics": {
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2025-9824",
"role": "CISA Coordinator",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"version": "2.0.3",
"timestamp": "2025-09-03T14:45:46.949698Z"
}
}
],
"cvssMetricV31": [
{
"type": "Secondary",
"source": "security@mautic.org",
"cvssData": {
"scope": "UNCHANGED",
"version": "3.1",
"baseScore": 5.9,
"attackVector": "NETWORK",
"baseSeverity": "MEDIUM",
"vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H",
"integrityImpact": "NONE",
"userInteraction": "NONE",
"attackComplexity": "HIGH",
"availabilityImpact": "HIGH",
"privilegesRequired": "NONE",
"confidentialityImpact": "NONE"
},
"impactScore": 3.6,
"exploitabilityScore": 2.2
}
]
},
"affected": [
{
"source": "security@mautic.org",
"affectedData": [
{
"repo": "https://github.com/mautic/mautic",
"vendor": "Mautic",
"product": "Mautic",
"versions": [
{
"status": "affected",
"version": ">= 4.4.0",
"lessThan": "< 4.4.17",
"versionType": "semver"
},
{
"status": "affected",
"version": ">= 5.0.0-alpha",
"lessThan": "< 5.2.8",
"versionType": "semver"
},
{
"status": "affected",
"version": ">= 6.0.0-alpha",
"lessThan": "< 6.0.5",
"versionType": "semver"
}
],
"packageName": "mautic/core",
"collectionURL": "https://packagist.org",
"defaultStatus": "unaffected"
}
]
}
],
"published": "2025-09-03T15:15:49.413",
"references": [
{
"url": "https://github.com/mautic/mautic/security/advisories/GHSA-3ggv-qwcp-j6xg",
"source": "security@mautic.org"
}
],
"vulnStatus": "Deferred",
"weaknesses": [
{
"type": "Secondary",
"source": "security@mautic.org",
"description": [
{
"lang": "en",
"value": "CWE-204"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "ImpactThe 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.\n\nPatchesThis vulnerability has been patched, implementing a timing-safe form login authenticator that ensures consistent response times regardless of whether a user exists or not.\n\nTechnical DetailsThe vulnerability was caused by different response times when:\n\n * A valid username was provided (password hashing occurred)\n * An invalid username was provided (no password hashing occurred)\n\n\nThe fix introduces a TimingSafeFormLoginAuthenticator that performs a dummy password hash verification even for non-existent users, ensuring consistent timing.\n\nWorkaroundsNo workarounds are available. Users should upgrade to the patched version.\n\nReferences * 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"
}
],
"lastModified": "2026-06-17T10:09:50.780",
"sourceIdentifier": "security@mautic.org"
}