CVE-2026-3688
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 WCFM Membership – WooCommerce Memberships for Multivendor Marketplace plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 2.11.10. This is due to the 'wcfmvm_membership_change' AJAX action not validating user permission to modify other users. This makes it possible for authenticated attackers, with vendor level access and above, to change any user's role to 'wcfm_vendor' by changing their membership plan.
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 WCFM Membership plugin contains an Insecure Direct Object Reference (IDOR) vulnerability in the wcfmvm_membership_change AJAX action. The plugin fails to validate that the authenticated user has permission to modify other users' membership plans, allowing any vendor-level user to arbitrarily change any other user's role to wcfm_vendor by manipulating the membership plan parameter.
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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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.
-
Confirm WCFM Membership plugin is installedLocate the plugin file (typically in wp-content/plugins/wcfm-membership or similar) or check WordPress plugin admin panel for 'WCFM Membership' entryAffected if The plugin is present on the WordPress site
-
Identify installed plugin versionCheck the plugin header in main PHP file (often wcfm-membership.php) for Version comment, or view in WordPress plugin admin panelAffected if Version cannot be verified as patched or version is unknown (defender must compare to known affected versions)
-
Verify wcfmvm_membership_change AJAX endpoint existsSearch plugin code for 'wcfmvm_membership_change' action hook registration (typically add_action('wp_ajax_wcfmvm_membership_change', ...))Affected if The AJAX action handler is registered and accessible to authenticated users
-
Confirm vendor-level user accounts existCheck WordPress user roles for users with 'wcfm_vendor' role or custom vendor roles created by the pluginAffected if There are users with vendor-level privileges who could potentially exploit this endpoint
-
Check for unexpected role changes to vendorReview user role changes in WordPress audit logs, user_meta tables, or plugin activity logs for any wcfm_vendor role assignments you did not initiateAffected if Users were changed to wcfm_vendor without explicit authorization
You are affected if WCFM Membership plugin is installed, the wcfmvm_membership_change AJAX action exists, and your site has vendor-level users who could manipulate other users' membership plans without proper authorization checks.
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 WCFM Membership plugin to the latest version, which should include proper authorization checks on the wcfmvm_membership_change AJAX action to verify the requesting user has permission to modify the target user's membership.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-3688 — 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-3688 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