CVE-2026-6897
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 unauthorized modification of data due to a missing capability check on the 'WishListMember\Features\Team_Accounts::save_settings' 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 arbitrary plugin options, includes 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 confidenceThe Wishlist Member WordPress plugin lacks a capability check on the WishListMember\Features\Team_Accounts::save_settings function, allowing any authenticated user with Subscriber-level access or higher to modify plugin settings. Attackers can update the REST API Secret Key, create new membership levels assigned administrator role, and register arbitrary admin accounts, 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 is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Wishlist Member', or check the plugins directory for wishlist-member folder, or query the database wp_options table for option_name='active_plugins'Affected if Wishlist Member plugin is not present in the WordPress installation
-
Check installed plugin versionIn WordPress admin, go to Plugins > Installed Plugins and click on 'View details' for Wishlist Member, or read version from wishlist-member/wishlist-member.php file header, or check wp_options for option_name containing 'wishlist_member' versionAffected if Version is present and is lower than 3.30.2 (e.g., 3.30.1, 3.30.0, etc.)
-
Confirm Team_Accounts feature is enabledCheck the Wishlist Member settings for Team Accounts feature status. This may be in plugin settings pages under Team/Team Accounts section, or inspect the database wp_options table for wishlist_member_team_accounts related optionsAffected if Team_Accounts feature is active/enabled in the plugin configuration
-
Verify user role configuration allows subscriber-level accessIn WordPress admin under Settings > General, check 'Default Role' setting, or review wp_options for 'default_role' value. Also check if any user roles above Subscriber exist that could be exploitedAffected if Default role is set to Subscriber or higher, or if subscriber-level users have any authenticated access to the site
A user is affected if Wishlist Member plugin versions prior to 3.30.2 are installed with Team_Accounts feature enabled, and the site permits subscriber-level authenticated users to access the system.
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 dataUpgrade to Wishlist Member version 3.30.2 or later. If immediate upgrade is not possible, disable the Team_Accounts feature and restrict user registration to trusted administrators only.
- Consultation3.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,416.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6897 — 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-6897 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