# CVE-2026-84795: Craft CMS before 5.10.11 Authentication Bypass via Admin Flag Inheritance

> Attackers can gain administrator privileges by registering with a deactivated admin's email if public registration and email verification are disabled.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-242m-9wq7-vhwq, GHSA-c8qg-58pw-vmfc

## What is CVE-2026-84795?

CVE-2026-84795 is a critical vulnerability in craftcms cms, published on 2 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Craft CMS before 5.10.11 fails to validate the admin flag during user registration, allowing it to persist from deactivated admin accounts. Attackers can register with a deactivated admin's email address to inherit administrator privileges when public registration and disabled email verification are configured.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-84795 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-84795 is a critical vulnerability in craftcms cms, published on 2 Sep 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-84795 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-84795/ (Markdown: https://insights.sbomify.com/CVE-2026-84795/index.md)
```

## Sources

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

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