CVE-2025-15147

WCFM Membership – WooCommerce Memberships for Multivendor Marketplace <= 2.11.8 - Insecure Direct Object Reference to Update Membership Payment

2026-02-09 11:17
Jing Xuan Sun

Strategic Overview

Status
Patched in 2.11.9
Affected Version
<= 2.11.8
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2025-15147
View all WCFM Membership – WooCommerce Memberships for Multivendor Marketplace vulnerabilities

At a glance

CVE-2025-15147 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WCFM Membership WordPress plugin, affecting versions <= 2.11.8. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The issue is fixed in version 2.11.9; sites on affected versions should update now. Disclosed February 2026, reported by Jing Xuan Sun.

Vulnerability Overview

The 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.8 via the 'WCFMvm_Memberships_Payment_Controller::processing' due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify other users' membership payments.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in WCFM Membership <= 2.11.8 takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For WCFM Membership the fix is 2.11.9: builds <= 2.11.8 are affected, anything from 2.11.9 onward is not.

Remediation

Update to version 2.11.9, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WCFM Membership 2.11.9 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C