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
Source GCVE Database
Not known to be exploited · CVSS 7.5 High.
Data as of 18 Nov 2026, 13:49 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 7.5 |
|---|
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| dokanincDokan: AI Powered WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy | Affected
| Fixed in– |
Description
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 `matches_mcp_endpoint()` function applies an unanchored regular expression (`#/(?:woocommerce|dokan)/mcp(?:/|$)#`) against the entire `REQUEST_URI` 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 `scope_product_permissions()` to unconditionally return `true` on WooCommerce's `woocommerce_rest_check_permissions` 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.
References
- nvd.nist.gov/vuln/detail/CVE-2026-119220 (opens in a new tab)
- plugins.trac.wordpress.org/browser/dokan-lite/tags/5.3.0/includes/Abilities/ProductAbilityScope.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/dokan-lite/tags/5.3.0/includes/Abilities/ProductAbilityScope.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/dokan-lite/tags/5.3.0/includes/Abilities/Support/RequestContext.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/dokan-lite/tags/5.3.0/includes/Abilities/Support/RequestContext.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?reponame=&old=3785932%40dokan-lite&new=3785932%40dokan-lite (opens in a new tab)
- wordfence.com/threat-intel/vulnerabilities/id/763f48c1-9686-4385-a78e-573d4bf2bae6?source=cve (opens in a new tab)