# CVE-2026-72786: Craft CMS 5.0.0-RC1 before 5.10.8 Authentication Bypass via Password Reset

> Authenticated users with edit permissions can bypass password verification to reset any user's password, including administrators, leading to account takeover.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Aug 2026
- **Updated:** 8 Oct 2026
- **Also known as:** GHSA-9j4x-96g5-572j

## What is CVE-2026-72786?

CVE-2026-72786 is a high-severity authentication bypass vulnerability in craftcms cms, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Craft CMS versions before 5.10.8 contain an authentication bypass vulnerability in the elements/save action that allows authenticated users to change passwords without verification. Attackers with edit users permission can reset any user's password including administrators by exploiting the unprotected newPassword field in the User element save flow.

Weakness: CWE-285 (Improper Authorization)

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


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

No fix has been published for CVE-2026-72786 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-72786 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-72786 is a high-severity authentication bypass vulnerability in craftcms cms, published on 12 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-72786 in the wild and no public exploit code.

Affected product: craftcms cms. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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