# CVE-2026-11966: User Registration & Membership < 5.2.3 - Unauthenticated Limited User Deletion via Stripe Subscription Handler

> Unauthenticated attackers can delete recently-registered user accounts by exploiting a missing capability check in the Stripe subscription handler.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-2wp6-4gxm-vfvx

## What is CVE-2026-11966?

CVE-2026-11966 is a medium-severity missing authorization vulnerability in Unknown User Registration & Membership, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The User Registration & Membership  WordPress plugin before 5.2.3 does not perform a capability check for unauthenticated callers on one of its membership payment actions and acts on a caller-supplied user identifier, allowing unauthenticated attackers to delete recently-registered, payment-pending user accounts.

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

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


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

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

## Is CVE-2026-11966 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11966 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-11966 is a medium-severity missing authorization vulnerability in Unknown User Registration & Membership, published on 17 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-11966 exists.

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

## Sources

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

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