Skip to main content

WCFM Frontend Manager CVE-2026-2554

| EUVDEUVD-2026-26789 HIGH
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-05-02 Wordfence
8.1
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain vendor account credentials
  2. Delivery
    Authenticate to WordPress dashboard
  3. Exploit
    Enumerate user IDs via REST API
  4. Execution
    Send crafted AJAX request to wcfm_delete_wcfm_customer
  5. Persist
    Delete administrator accounts
  6. Impact
    Escalate privileges to site control

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

Requires authenticated access with WordPress Vendor role or higher capability within the WCFM plugin permission system. The attacker must have a legitimate vendor account on the target WooCommerce marketplace-either through social engineering to pass vendor vetting processes, or by compromising existing vendor credentials. Default WCFM installations with open vendor registration are at highest risk. Vulnerability is exploitable against any WordPress site running WCFM versions ≤6.7.25 where the vendor role has access to customer management functions. No specific WooCommerce configuration, PHP version, or server-side settings limit exploitation beyond the fundamental requirement of vendor-level authentication.

Impact

Real-world risk is HIGH for WooCommerce marketplace operators but requires insider threat scenario. CVSS 8.1 (AV:N/AC:L/PR:L/UI:N) indicates network-accessible exploitation with low complexity once vendor credentials are obtained, with high integrity and availability impact (deleting admin accounts effectively compromises site control). However, PR:L (low privileges required) means attackers must first obtain legitimate vendor account credentials, limiting opportunistic exploitation. No EPSS score, KEV listing, or public POC identified, suggesting purely theoretical exploitation status. SSVC framework assessment: exploitation not confirmed, requires authenticated access (not automatable against arbitrary targets), technical impact is total (admin deletion = full site compromise). Priority depends on vendor vetting practices: high-trust vendor programs face lower risk than open vendor registration. Missing vendor advisory makes patch adoption tracking difficult.

Exploit ScenarioDerived

A malicious actor registers as a legitimate vendor on a WooCommerce marketplace running WCFM plugin version 6.7.24. After account approval, the attacker crafts authenticated requests to the 'wcfm_delete_wcfm_customer' AJAX endpoint, iterating through user IDs to identify and delete administrator accounts (typically user ID 1-10 in WordPress). With administrators removed, the attacker either promotes their vendor account to admin via database manipulation or exploits the power vacuum to take control through remaining lower-privileged accounts. The low attack complexity (AC:L) means exploitation requires only basic understanding of WordPress user ID enumeration and AJAX endpoint interaction.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – May 02, 2026

Authenticated vendors with low-level privileges can delete arbitrary WordPress users, including site administrators, via Insecure Direct Object Reference in WCFM - Frontend Manager for WooCommerce plugin versions up to 6.7.25. The vulnerability resides in the 'wcfm_delete_wcfm_customer' function which fails to validate user-controlled 'customerid' parameters, allowing privilege escalation through unauthorized user deletion. Patch available in version 6.7.26 per Trac changeset 3483695. No public exploit code or active exploitation confirmed at time of analysis, though CVSS 8.1 (High) reflects significant real-world impact if exploited by malicious vendors on WooCommerce marketplaces.

RemediationAI

Upgrade to WCFM - Frontend Manager for WooCommerce version 6.7.26 or later, which implements proper authorization checks per WordPress Trac changeset 3483695 (https://plugins.trac.wordpress.org/changeset/3483695/). If immediate patching is infeasible, implement compensating controls: (1) Audit and restrict vendor role assignment to only thoroughly vetted merchants, eliminating untrusted vendor accounts. Trade-off: impacts marketplace growth but prevents malicious vendor enrollment. (2) Enable WordPress activity logging (plugins like WP Activity Log) to detect suspicious user deletion events, particularly admin account removals by vendor-role users. Trade-off: detective not preventive control, requires active monitoring. (3) Database-level triggers or backup retention policies to enable rapid admin account restoration. Trade-off: mitigates availability impact but does not prevent initial compromise. No workaround fully eliminates risk without vendor-supplied patch addressing root CWE-639 authorization bypass.

Affected VersionsENISA

WCFM – Frontend Manager for WooCommerce 0 ≤6.7.25

Affected Packages

euvd wcfm_frontend_manager_for_woocommerce no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

WCFM - Frontend Manager for WooCommerce (cpe:2.3:a:wclovers:wcfm_-_frontend_manager_for_woocommerce) is a WordPress plugin enabling multi-vendor marketplace functionality for WooCommerce stores. The vulnerability stems from CWE-639 (Authorization Bypass Through User-Controlled Key), where the class-wcfm-customer.php delete function accepts a 'customerid' parameter without verifying the requesting user has authority over that specific customer record. WordPress capability checks verify the requester has 'vendor' role but do not enforce object-level authorization, allowing horizontal privilege escalation to manipulate any user ID. This IDOR pattern is particularly severe in multi-vendor platforms where vendors should only access their own customer data, not platform administrators or other vendors' accounts.

Know when Wcfm Frontend Manager For Woocommerce gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 8.1 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

WCFM - Frontend Manager for WooCommerce versions up to 6.7.25 contain a critical privilege escalation vulnerability allowing authenticated vendors to delete arbitrary WordPress users, including administrators, through insecure object reference handling. This directly threatens site availability and administrative control on WooCommerce installations, particularly those operating multi-vendor marketplaces where vendor accounts have system access.

Business Impact: High
Compensating Controls

Vendor-released patch: version 6.7.26. Until patching is complete: (1) Disable vendor deletion permissions at the application role level if plugin settings permit; (2) Implement database-level access controls limiting vendor role modification queries; (3) Enable audit logging for user account modifications and monitor for suspicious deletion events; (4) Restrict high-privilege vendor accounts and require administrative approval for any new vendor onboarding.

Threat Intelligence Overview

EPSS Score
0.0%
Top 90% exploitable
Data Quality
6 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy