# CVE-2026-44306: Statamic: Email enumeration via forgot password endpoint

> An unauthenticated attacker can enumerate valid user accounts via the forgot password endpoint, aiding credential attacks.

- **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:** 12 May 2026
- **Updated:** 13 May 2026
- **Also known as:** GHSA-m24v-f7g5-gq67

## What is CVE-2026-44306?

CVE-2026-44306 is a medium-severity vulnerability in statamic cms, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Statamic is a Laravel and Git powered content management system (CMS). Prior to 5.73.21 and 6.15.0, responses from the forgot password forms hinted at whether an account existed for a given email address. An unauthenticated attacker could use this to enumerate valid users, which can aid in follow-up credential-based attacks. This vulnerability is fixed in 5.73.21 and 6.15.0.

Weakness: CWE-204 (Observable Response Discrepancy)

## Which versions are affected by CVE-2026-44306?

4 open source packages ship an affected version, including statamic/cms.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `statamic/cms` | Packagist | All versions | 5.73.21 |
| `statamic/cms` | Packagist | All versions | 5.73.21 |
| `statamic/cms` | Packagist | From 6.0.0 | 6.15.0 |
| `statamic/cms` | Packagist | From 6.0.0 | 6.15.0 |

## How do I fix CVE-2026-44306?

Upgrade statamic/cms to a fixed version for your release line: 5.73.21 or 6.15.0.

## Is CVE-2026-44306 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44306 and fix it if it is affected.

What it is: CVE-2026-44306 is a medium-severity vulnerability in statamic cms, published on 12 May 2026. 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-2026-44306 in the wild and no public exploit code.

Affected packages and fixed versions:
- statamic/cms (Packagist): affected all versions; fixed in 5.73.21
- statamic/cms (Packagist): affected all versions; fixed in 5.73.21
- statamic/cms (Packagist): affected from 6.0.0; fixed in 6.15.0
- statamic/cms (Packagist): affected from 6.0.0; fixed in 6.15.0

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-2026-44306/ (Markdown: https://insights.sbomify.com/CVE-2026-44306/index.md)
```

## Sources

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

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