# CVE-2026-79995: User Registration & Membership < 5.2.5 - Subscriber+ Pending Email Change Cancellation via IDOR

> Authenticated users can cancel pending email changes for any other user, including administrators, due to missing ownership verification.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A: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:** 28 Aug 2026
- **Updated:** 28 Aug 2026
- **Also known as:** GHSA-mfx5-4qv9-69f3

## What is CVE-2026-79995?

CVE-2026-79995 is a medium-severity missing authorization vulnerability in Unknown User Registration & Membership, published on 28 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The User Registration & Membership  WordPress plugin before 5.2.5 does not verify that the account whose pending email change is being cancelled belongs to the user making the request, allowing authenticated users with Subscriber-level access and above to cancel any other user's in-progress email change, including an administrator's.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-79995 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-79995 is a medium-severity missing authorization vulnerability in Unknown User Registration & Membership, published on 28 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-79995 in the wild and no public exploit code.

Affected product: Unknown User Registration & Membership. 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-79995/ (Markdown: https://insights.sbomify.com/CVE-2026-79995/index.md)
```

## Sources

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

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