CVE-2026-119220: Dokan: AI Powered WooCommerce Multivendor Marketplace Solution <= 5.3.3 - Authorization Bypass via '/dokan/mcp/' Marker in REQUEST_URI
The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy plugin for WordPress is vulnerable to Authorization Bypass in all versions up to, and including, 5.3.3. The vulnerability exists because the matchesmcpendpoint() function applies an unanchored regular expression (#/(?:woocommerce|dokan)/mcp(?:/|$)#) against the entire REQUESTURI including the query string, meaning any request that contains the literal substring /dokan/mcp/ or /woocommerce/mcp/ anywhere in its URI — including inside a query parameter value — is incorrectly treated as a trusted internal MCP context, causing scopeproductpermissions() to unconditionally return true on WooCommerce's woocommercerestcheckpermissions filter regardless of whether the caller is authenticated. This makes it possible for unauthenticated attackers to read full authenticated WooCommerce REST product records for any published product — including private underscore-prefixed meta, purchase notes, downloadable file URLs for paid digital products, catalog-hidden products, and edit-context representations — across the /wc/v1, /wc/v2, /wc/v3, and /wc-analytics REST namespaces. The bypass is triggered by appending a query parameter whose value contains the literal string /dokan/mcp/ to any WooCommerce REST product endpoint (e.g., /wp-json/wc/v3/products/{id}?x=/dokan/mcp/); note that percent-encoding the slashes prevents the bypass, as the unencoded literal slash characters are required for the regex to match.
Affected Software
Event History
Frequently Asked Questions
Which installations are affected?
All versions of the Dokan plugin up to and including 5.3.3 are affected.
Does exploitation require a WordPress or WooCommerce account?
No. An unauthenticated attacker can trigger the bypass by including the literal /dokan/mcp/ or /woocommerce/mcp/ substring anywhere in the request URI, including in a query parameter value.
What information could be exposed?
Attackers can read full authenticated WooCommerce REST product records for published products. Exposed data can include private underscore-prefixed metadata, purchase notes, downloadable file URLs for paid digital products, catalog-hidden products, and edit-context representations.
Which REST API areas are implicated?
The issue affects product-record access through the /wc/v1, /wc/v2, /wc/v3, and /wc-analytics REST namespaces.