CVE-2026-119220 json
Dokan: AI Powered WooCommerce Multivendor Marketplace Solution <= 5.3.3 - Authorization Bypass via '/dokan/mcp/' Marker in REQUEST_URI
published 15h ago modified 10h ago also EUVD-2026-128558
- cvss
- 7.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- —
- no EPSS score yet
- public exploits
- 0
- none known
Summary
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.
Is CVE-2026-119220 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 11h ago
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N |
Affected products
- dokaninc Dokan: AI Powered WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy
Classification
- Weakness
-
- CWE-285 Improper Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/763f48c1-9686-4385-a78e-573d4bf2bae6?source=cve
- plugins.trac.wordpress.org /browser/dokan-lite/tags/5.3.0/includes/Abilities/Support/RequestContext.php#L223
- plugins.trac.wordpress.org /browser/dokan-lite/tags/5.3.0/includes/Abilities/Support/RequestContext.php#L94
- plugins.trac.wordpress.org /browser/dokan-lite/tags/5.3.0/includes/Abilities/ProductAbilityScope.php#L179
- plugins.trac.wordpress.org /browser/dokan-lite/tags/5.3.0/includes/Abilities/ProductAbilityScope.php#L150
- plugins.trac.wordpress.org /changeset?reponame=&old=3785932%40dokan-lite&new=3785932%40dokan-lite
Sources
- CVE List CVE-2026-119220
- NVD CVE-2026-119220
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.