# CVE-2026-86407: User Registration & Membership < 5.2.8 - Unauthenticated User Data Disclosure via Membership Thank You Page

> Unauthenticated attackers can retrieve sensitive user data from the membership confirmation page if specific smart tags are configured.

- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/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:** 13 Sep 2026
- **Updated:** 13 Sep 2026
- **Also known as:** GHSA-wr2r-r9vc-rr7g

## What is CVE-2026-86407?

CVE-2026-86407 is a low-severity vulnerability in Unknown User Registration & Membership, published on 13 Sep 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.8 does not verify that the visitor requesting its membership confirmation page owns the account named in the request, nor that any registration or purchase has taken place, allowing unauthenticated users to retrieve another user's email address, profile fields, role and membership order details. Exploitation requires the site owner to have added a user smart tag to that page's configurable message, which the shipped default does not contain.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-86407 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86407 is a low-severity vulnerability in Unknown User Registration & Membership, published on 13 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-86407 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-86407/ (Markdown: https://insights.sbomify.com/CVE-2026-86407/index.md)
```

## Sources

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

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