CVE-2026-4896
Received Received - Intake
Insecure Direct Object Reference in WCFM Plugin Allows Order and Content Manipulation

Publication date: 2026-04-04

Last updated on: 2026-04-04

Assigner: Wordfence

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-04
Last Modified
2026-04-04
Generated
2026-05-07
AI Q&A
2026-04-04
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
wcmarketplace wcfm_frontend_manager 6.7.25
wcmarketplace wcfm_frontend_manager to 6.7.25 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The vulnerability in the WCFM – Frontend Manager for WooCommerce and Bookings Subscription Listings Compatible plugin for WordPress is an Insecure Direct Object Reference (IDOR). It affects all versions up to and including 6.7.25. The issue arises because multiple AJAX actions, such as `wcfm_modify_order_status`, `delete_wcfm_article`, and `delete_wcfm_product`, do not properly validate user-supplied object IDs.

This lack of validation allows authenticated users with Vendor-level access or higher to manipulate objects they do not own. Specifically, they can modify the status of any order or delete or modify any post, product, or page regardless of ownership.


How can this vulnerability impact me? :

This vulnerability can have serious impacts including unauthorized modification or deletion of orders, posts, products, or pages within the WooCommerce environment. An attacker with Vendor-level access can change order statuses arbitrarily or remove content they should not have control over.

Such actions can disrupt business operations, cause data loss, and potentially lead to financial or reputational damage.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability involves insecure direct object references in AJAX actions such as `wcfm_modify_order_status`, `delete_wcfm_article`, and `delete_wcfm_product` due to missing validation on user-supplied object IDs.

To detect exploitation attempts on your system, you can monitor HTTP requests targeting these AJAX endpoints for suspicious activity, especially requests made by authenticated users with Vendor-level access or higher.

Suggested commands include using web server logs or network monitoring tools to filter for POST requests containing these AJAX actions. For example, using grep on Apache or Nginx logs:

  • grep -i 'wcfm_modify_order_status' /var/log/apache2/access.log
  • grep -i 'delete_wcfm_article' /var/log/apache2/access.log
  • grep -i 'delete_wcfm_product' /var/log/apache2/access.log

Additionally, monitoring for unexpected changes in order statuses, deleted or modified posts/products/pages by vendors can indicate exploitation.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include restricting access to the affected AJAX actions to only trusted users and roles, ensuring proper validation of user-supplied object IDs, and applying any available patches or updates to the WCFM plugin.

Since the vulnerability affects all versions up to and including 6.7.25, upgrading the plugin to a fixed version (if available) is critical.

If an immediate update is not possible, consider temporarily disabling the vulnerable AJAX actions or limiting vendor permissions to prevent unauthorized modifications.

Monitoring and auditing vendor activities for suspicious changes can also help mitigate impact.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows 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 due to missing validation on user-supplied object IDs.

Such unauthorized modifications could lead to data integrity issues and unauthorized data manipulation, which may impact compliance with standards and regulations that require strict access controls and data protection, such as GDPR and HIPAA.

However, the provided information does not explicitly describe the direct impact on compliance with these regulations.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart