Skip to main content

Wcfm Frontend Manager For Woocommerce EUVDEUVD-2026-18981

| CVE-2026-4896 HIGH
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-04-04 Wordfence GHSA-mjxj-p494-qx82
8.1
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

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

  1. Access
    Authenticate as vendor user
  2. Exploit
    Call wcfm_modify_order_status AJAX action
  3. Execution
    Supply arbitrary order ID without validation
  4. Impact
    Modify any order status in system

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 WordPress user with Vendor-level access or higher to WCFM plugin. Attacker exploits AJAX actions (wcfm_modify_order_status, delete_wcfm_article, delete_wcfm_product) in plugin versions up to 6.7.25 by supplying arbitrary object IDs to modify/delete orders and posts across all vendors.

Impact

The CVSS 8.1 HIGH rating reflects network-based exploitation (AV:N) with low complexity (AC:L) and no user interaction (UI:N), requiring only low-privileged vendor credentials (PR:L). High integrity and availability impact (I:H/A:H) accurately captures the ability to alter order statuses marketplace-wide and delete critical content, potentially causing business disruption and data loss. However, real-world risk depends heavily on deployment context: WooCommerce stores using WCFM with multiple vendor accounts face elevated exposure, as any compromised or malicious vendor can sabotage competitors' products, manipulate financial transactions, or delete store pages. The authentication requirement (PR:L) reduces surface area compared to unauthenticated flaws, but vendor registration is often self-service in marketplace implementations. No public exploit identified at time of analysis, though IDOR vulnerabilities are trivially exploitable once endpoint details are known-expect rapid weaponization post-disclosure. Without EPSS data or KEV listing, prioritization should focus on stores with untrusted vendor populations or those processing high transaction volumes where order manipulation poses financial/reputational harm.

Exploit ScenarioDerived

A malicious actor registers a vendor account on a WooCommerce marketplace running vulnerable WCFM plugin versions, gaining legitimate low-privileged credentials through standard self-service onboarding. Using browser developer tools or intercepting proxy, the attacker crafts POST requests to the wcfm_modify_order_status AJAX endpoint, iterating through sequential order IDs to change high-value orders to 'cancelled' status, disrupting competitor sales and creating customer service chaos. Simultaneously, they invoke delete_wcfm_product with enumerated product IDs belonging to rival vendors, purging their catalog entries and causing immediate revenue loss. The attack requires only knowledge of WordPress AJAX endpoint conventions and minimal technical sophistication, with exploitation complexity rated low (AC:L) as no cryptographic bypass or race conditions are necessary-simple parameter manipulation achieves unauthorized access to global store resources.

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 – Apr 04, 2026

Insecure Direct Object Reference in WCFM Frontend Manager for WooCommerce (versions ≤6.7.25) allows authenticated vendors to manipulate arbitrary orders and delete any WordPress posts, products, or pages beyond their ownership scope. Exploitation requires only vendor-level credentials (PR:L) with no user interaction, enabling privilege escalation through unauthorized access to store-wide content. EPSS data not available; no public exploit identified at time of analysis, though the vulnerability's straightforward IDOR nature increases weaponization risk once details are public.

RemediationAI

Upgrade WCFM Frontend Manager for WooCommerce to version 6.7.26 or later, which addresses the IDOR vulnerabilities through implementation of proper authorization checks on AJAX endpoints processing user-supplied object IDs. Site administrators should audit existing vendor accounts for suspicious activity, reviewing order status modification logs and checking for unexpected post/product deletions that may indicate prior exploitation. As an interim mitigation if immediate patching is infeasible, restrict vendor account creation to trusted users and implement additional monitoring on the identified AJAX actions (wcfm_modify_order_status, delete_wcfm_article, delete_wcfm_product) through WordPress security logging plugins. Consult the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/f8248098-dff2-4bac-a138-aa40c7ab7a1c for additional context. For development teams, review the patched code paths in versions post-6.7.25 available via WordPress plugin repository to understand the corrected authorization logic pattern for user-controlled resource identifiers.

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 (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 multiple AJAX endpoints-including wcfm_modify_order_status, delete_wcfm_article, delete_wcfm_product, and the article management controller-accept user-supplied object IDs without validating ownership or authorization boundaries. Per Wordfence source code analysis, these endpoints process resource identifiers directly from request parameters without cross-referencing the requesting user's permissions against the target object's ownership metadata. This violates the principle of complete mediation, allowing low-privileged vendor accounts to reference and manipulate global WordPress post IDs, WooCommerce order IDs, and product IDs that should be restricted to administrators or their actual owners.

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

Vendor (Wordfence) PRIMARY 8.1 HIGH
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H

Primary rating from Vendor (Wordfence) · only source for this CVE.

CVSS VectorVendor: Wordfence

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

Lifecycle Timeline

2
PoC Detected
Apr 07, 2026 - 13:20 vuln.today
Public exploit code
CVE Published
Apr 04, 2026 - 07:42 nvd
HIGH 8.1

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 multiple AJAX actions including wcfm_modify_order_status, delete_wcfm_article, delete_wcfm_product, and the article management controller due to missing validation on user-supplied object IDs. This makes it possible for authenticated attackers, with Vendor-level access and above, to modify the status of any order, delete or modify any post/product/page, regardless of ownership.

Executive ViewAI

Why It Matters

WCFM Frontend Manager for WooCommerce versions 6.7.25 and earlier contain an insecure direct object reference vulnerability that permits authenticated vendors to manipulate orders and delete arbitrary site content (posts, products, pages) regardless of ownership. This privilege escalation risk exposes store operations to data loss, inventory disruption, and competitive sabotage by malicious insiders or compromised vendor accounts, requiring immediate action for any organization using this plugin.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict WCFM vendor roles to read-only access where operationally feasible; (2) implement WordPress role-based access control (RBAC) to limit vendor capabilities at the application level; (3) enable comprehensive audit logging of vendor account actions (order modifications, post/product deletions); (4) enforce multi-factor authentication (MFA) on all vendor accounts to reduce compromise risk; (5) consider disabling the plugin entirely on non-critical sites until a patch is released; (6) monitor vendor user sessions and implement IP whitelisting if vendor operations are geographically confined.

Threat Intelligence Overview

EPSS Score
0.0%
Top 99% exploitable
Exploit
POC
Public exploit code exists
Social Media
3
Sightings
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

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 Yes
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
Total

Priority Score

60
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: +20
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