dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-6898

HIGH · 8.8 CVSS v3.1 Published 2026-05-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
The Wishlist Member plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the 'WishListMember3_Hooks::generate_api_key' function in all versions up to, and including, 3.30.1. This makes it possible for authenticated attackers, with Subscriber-level access and above, to update the REST API Secret Key, which can be used to 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 confidence

The Wishlist Member plugin for WordPress has a broken access control vulnerability in the generate_api_key function. The function lacks a capability check, allowing any authenticated user with Subscriber-level access or higher to call it. Attackers can update the REST API Secret Key, create membership levels with Administrator role, and register new admin accounts, achieving full site compromise.

MitigationUpdate to Wishlist Member version 3.30.2 or later which includes the missing capability check. Until patched, consider restricting REST API access or temporarily disabling the plugin if running a version before 3.30.2.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Wishlist Member plugin is installed
    Go to WordPress admin > Plugins and look for 'Wishlist Member' in the installed plugins list, or check the plugins directory for /wp-content/plugins/wishlist-member/
    Affected if The plugin is installed and active
  2. Determine installed Wishlist Member version
    In WordPress admin > Plugins, find Wishlist Member and note the version number displayed under the plugin name, or inspect the main plugin file header for the Version field
    Affected if Version is below 3.30.2 (the vulnerability is present in versions prior to 3.30.2)
  3. Confirm REST API functionality is enabled
    Check if WordPress REST API is accessible by visiting /wp-json/ in a browser, or verify the Wishlist Member API settings are accessible in the plugin admin panel under WishList Member > Settings > API
    Affected if REST API endpoints are accessible and the Wishlist Member API module is enabled
  4. Review user accounts with Subscriber role
    In WordPress admin > Users, examine all users with the Subscriber role. Any subscriber-level account could have exploited this vulnerability to escalate privileges
    Affected if There are Subscriber-level users present in the system who should not have been granted API access
  5. Audit for unauthorized Administrator accounts
    In WordPress admin > Users, check for Administrator accounts that you did not create. Also check Wishlist Member > Membership Levels to see if any levels grant administrator-level capabilities
    Affected if There are Administrator accounts or membership levels with admin privileges that you did not explicitly create

If Wishlist Member is installed with a version below 3.30.2 and any authenticated users with Subscriber-level access exist in the system, the environment may be affected by this privilege escalation vulnerability.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to Wishlist Member version 3.30.2 or later which includes the missing capability check. Until patched, consider restricting REST API access or temporarily disabling the plugin if running a version before 3.30.2.

Recommended fix High confidence

Latest version of Wishlist Member plugin (after 3.30.1)

  1. Update the Wishlist Member plugin to the latest available version from the WordPress plugin repository or wishlistmember.com
  2. Verify that the updated version is higher than 3.30.1
  3. After updating, confirm that the generate_api_key function now includes proper capability checks
  4. Review user accounts with administrator roles created since the vulnerability was discovered

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,210
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,936.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6898 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6898 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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