CVE-2026-6895
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe WishList Member WordPress plugin lacks authorization checks in its 'export_settings' AJAX function, allowing unauthenticated attackers to retrieve the REST API Secret Key. This key can then be used via the WishList Member API to create administrator-level membership roles and register new admin users, achieving full site compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify WishList Member plugin installationCheck your WordPress installation for the WishList Member plugin. In WordPress admin, go to Plugins > Installed Plugins and look for 'WishList Member'. Note the installed version number.Affected if WishList Member plugin is installed and running, regardless of version (no version range was specified for this CVE)
-
Check for accessible export_settings AJAX endpointTest if the WordPress AJAX endpoint /wp-admin/admin-ajax.php?action=export_settings is accessible without authentication. This can be done with a curl request: curl -s 'https://yourdomain.com/wp-admin/admin-ajax.php?action=export_settings'. If the response contains a REST API Secret Key, the vulnerability is present.Affected if The AJAX endpoint returns the REST API Secret Key without requiring authentication or capability checks
-
Inspect REST API Secret Key exposureIf the AJAX endpoint is accessible, examine the response for a 'secret_key', 'api_secret', or similar field containing a long alphanumeric string. This key should not be exposed to unauthenticated users.Affected if The REST API Secret Key is visible in the unauthenticated AJAX response
-
Audit administrator user accountsIn WordPress admin, go to Users > All Users and review all accounts with the Administrator role. Look for unfamiliar administrator accounts that were created recently or without your knowledge.Affected if There are administrator accounts you did not create, indicating possible exploitation
-
Review WishList Member membership levelsIn WishList Member settings, go to Membership Levels and check if any levels have been created with Administrator role capabilities or can create administrator users. Look for unexpected levels you did not configure.Affected if Unexpected membership levels exist that grant administrator privileges or can register admin users
Your environment is affected if the WishList Member plugin is installed and the export_settings AJAX endpoint exposes the REST API Secret Key without authentication, or if unauthorized administrator accounts or membership levels exist on your site.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the WishList Member plugin to a version beyond 3.30.1 once available; immediately audit existing user accounts for unauthorized administrators and rotate the REST API secret key as a precaution.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6895 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6895 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data