# CVE-2026-6895: Missing authorization in Wishlist Member

> Missing authorization in Wishlist Member allows authenticated users to disclose API keys and escalate privileges to administrator.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 23 May 2026
- **Updated:** 26 May 2026
- **Also known as:** GHSA-7f9p-fmh2-r992

## What is CVE-2026-6895?

CVE-2026-6895 is a high-severity missing authorization vulnerability in Wishlist Member, published on 23 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WishList Member plugin for WordPress is vulnerable to Missing Authorization leading to Sensitive Information Disclosure and Privilege Escalation in versions up to and including 3.30.1. This is due to the missing capability checks in the 'export_settings' function. This function returns the REST API Secret Key to the attacker in the AJAX JSON response. An attacker who obtains this key can authenticate to the WishList Member API, create a new membership level assigned the administrator WordPress role, and register an arbitrary administrator-level user account, resulting in complete site takeover.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-6895 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-6895 is a high-severity missing authorization vulnerability in Wishlist Member, published on 23 May 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-6895 in the wild and no public exploit code.

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

## Sources

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

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