CVE-2026-2554

WCFM – Frontend Manager for WooCommerce along with Bookings Subscription Listings Compatible <= 6.7.25 - Authenticated (Vendor+) Insecure Direct Object Reference to Arbitrary User Deletion

2026-05-01 00:00
Supakiad S. (m3ez)

Strategic Overview

Status
Patched in 6.7.26
Affected Plugin
WCFM – Frontend Manager for WooCommerce
Affected Version
<= 6.7.25
CVSS
8.1High
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-2554
View all WCFM – Frontend Manager for WooCommerce vulnerabilities

At a glance

CVE-2026-2554 is a high-severity Authorization Bypass Through User-Controlled Key vulnerability in the WCFM WordPress plugin, affecting versions <= 6.7.25. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at Vendor level or above. The issue is fixed in version 6.7.26; sites on affected versions should update now. Disclosed May 2026, reported by Supakiad S. (m3ez).

Vulnerability Overview

The WCFM – Frontend Manager for WooCommerce along with Bookings Subscription Listings Compatible plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 6.7.25 via the 'wcfm_delete_wcfm_customer' due to missing validation on the 'customerid' user controlled key. This makes it possible for authenticated attackers, with Vendor-level access and above, to delete arbitrary users, including Administrators.

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. A successful exploit has high impact on integrity, availability.

CWE-639: Authorization Bypass Through User-Controlled Key

WCFM <= 6.7.25 carries this weakness at wcfm_delete_wcfm_customer, and reaching it takes an account at Vendor level or above. 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 the fix is 6.7.26: builds <= 6.7.25 are affected, anything from 6.7.26 onward is not.

Remediation

Update to version 6.7.26, 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 6.7.26 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-2554https://www.wordfence.com/threat-intel/vulnerabilities/id/21e397a4-0b32-4b13-a46b-c465acea0796https://nvd.nist.gov/vuln/detail/CVE-2026-2554

Related records

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