# CVE-2026-19423: Ultimate Member 2.6.7 - 2.12.1 - Unauthenticated Privilege Escalation via Role Field on Profile Forms

> Unauthenticated attackers can escalate privileges to administrator by manipulating role fields during registration in the Ultimate Member WordPress plugin.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-g9rf-98hp-9vc3

## What is CVE-2026-19423?

CVE-2026-19423 is a high-severity vulnerability in Unknown Ultimate Member, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Ultimate Member  WordPress plugin before 2.13.0 does not validate a submitted role selection when it cannot resolve the set of roles a profile form permits, and screens the value against the site's registered role names rather than against the form's own allow-list, allowing unauthenticated users who register through the Ultimate Member  WordPress plugin before 2.13.0's own form to grant themselves arbitrary capabilities and reach administrator-equivalent access.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-19423 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19423 is a high-severity vulnerability in Unknown Ultimate Member, published on 28 Aug 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-19423 in the wild and no public exploit code.

Affected product: Unknown Ultimate Member. 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-19423/ (Markdown: https://insights.sbomify.com/CVE-2026-19423/index.md)
```

## Sources

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

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