# CVE-2024-47057: User name enumeration possible due to response time difference on password reset form

> Unauthenticated attackers can enumerate valid usernames in Mautic by analyzing response time differences on the password reset form.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2025
- **Updated:** 29 May 2025
- **Also known as:** CVE-2025-48870, GHSA-424x-cxvh-wq9p

## What is CVE-2024-47057?

CVE-2024-47057 is a medium-severity vulnerability in Mautic, published on 28 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SummaryThis advisory addresses a security vulnerability in Mautic related to the "Forget your password" functionality. This vulnerability could be exploited by unauthenticated users to enumerate valid usernames.

User Enumeration via Timing Attack: A user enumeration vulnerability exists in the "Forget your password" functionality. Differences in response times for existing and non-existing users, combined with a lack of request limiting, allow an attacker to determine the existence of usernames through a timing-based attack.

MitigationPlease update to a version that addresses this timing vulnerability, where password reset responses are normalized to respond at the same time regardless of user existence.

Weakness: CWE-203 (Observable Discrepancy)

## Which versions are affected by CVE-2024-47057?

6 open source packages ship an affected version, including mautic/core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mautic/core` | Packagist | From 1.0.0 | 4.4.16 |
| `mautic/core` | Packagist | From 1.0.0 | 4.4.16 |
| `mautic/core` | Packagist | From 5.0.0-alpha | 5.2.6 |
| `mautic/core` | Packagist | From 5.0.0-alpha | 5.2.6 |
| `mautic/core` | Packagist | From 6.0.0-alpha | 6.0.2 |
| `mautic/core` | Packagist | From 6.0.0-alpha | 6.0.2 |

## How do I fix CVE-2024-47057?

Upgrade mautic/core to a fixed version for your release line: 4.4.16, 5.2.6 or 6.0.2.

## Is CVE-2024-47057 being exploited?

There is no known exploitation of CVE-2024-47057 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47057 and fix it if it is affected.

What it is: CVE-2024-47057 is a medium-severity vulnerability in Mautic, published on 28 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-47057 in the wild and no public exploit code.

Affected packages and fixed versions:
- mautic/core (Packagist): affected from 1.0.0; fixed in 4.4.16
- mautic/core (Packagist): affected from 1.0.0; fixed in 4.4.16
- mautic/core (Packagist): affected from 5.0.0-alpha; fixed in 5.2.6
- mautic/core (Packagist): affected from 5.0.0-alpha; fixed in 5.2.6
- mautic/core (Packagist): affected from 6.0.0-alpha; fixed in 6.0.2
- mautic/core (Packagist): affected from 6.0.0-alpha; fixed in 6.0.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-47057/ (Markdown: https://insights.sbomify.com/CVE-2024-47057/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-47057
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-47057
- OSV: https://osv.dev/vulnerability/CVE-2024-47057

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-47057/
Summaries are generated and may contain mistakes; the official description above is the record.