CVE-2026-1722

WCFM Marketplace <= 3.7.0 - Insecure Direct Object Reference to Unauthenticated Arbitrary Refund Request Creation

2026-02-09 18:54
Gibran Abdillah

Strategic Overview

Status
Patched in 3.7.1
Affected Plugin
WCFM Marketplace – Multivendor Marketplace for WooCommerce
Affected Version
<= 3.7.0
CVSS
5.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-1722
View all WCFM Marketplace – Multivendor Marketplace for WooCommerce vulnerabilities

At a glance

CVE-2026-1722 is a medium-severity Missing Authorization vulnerability in the WCFM Marketplace WordPress plugin, affecting versions <= 3.7.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.7.1; sites on affected versions should update now. Disclosed February 2026, reported by Gibran Abdillah.

Vulnerability Overview

The WCFM Marketplace – Multivendor Marketplace for WooCommerce plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.7.0. This is due to the plugin not implementing authorization checks in the `wcfm-refund-requests-form` AJAX controller. This makes it possible for unauthenticated attackers to create arbitrary refund requests for any order ID and item ID, potentially leading to financial loss if automatic refund approval is enabled in the plugin settings.

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 privileges on the target site, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in WCFM Marketplace <= 3.7.0 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WCFM Marketplace the fix is 3.7.1: builds <= 3.7.0 are affected, anything from 3.7.1 onward is not.

Remediation

Update to version 3.7.1, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WCFM Marketplace 3.7.1 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-1722https://www.wordfence.com/threat-intel/vulnerabilities/id/d39ec46d-58c4-40e4-b94a-e7a9fc99291ahttps://nvd.nist.gov/vuln/detail/CVE-2026-1722

Related records

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