Skip to main content
Menu
CVEs

CVE

Dokan: AI Powered WooCommerce Multivendor Marketplace Solution authorization bypass in REST product endpoint

CVE-2026-119220EUVD-2026-128558GHSA-FR8V-22HH-89VJPublished Updated Summary written by a model

7.5HighCNA
Exploited
No known exploitation
Fix
No fix listed
Who is exposed
Not reported

Summary

Dokan, a WooCommerce multivendor marketplace plugin for WordPress, has an authorization bypass that lets an unauthenticated attacker remotely, without logging in, read full WooCommerce product records for published products, including private meta, purchase notes, and download file URLs for paid digital products. The bypass is triggered by adding a query parameter that contains the literal path "/dokan/mcp/" to a WooCommerce REST product request.

Original 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.

cve.now Index

33Pcve.now Index 33 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed per the CVSS vector, CISA rates it automatable · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity7.5/10CVSS 7.5
  • No patch5/5No patch listed yet

What would change the score

  • Would score about 78 if added to CISA KEV
  • Would score about 73 if CISA's SSVC rates exploitation active
  • Would score about 38 if advisories confirm default setups are exposed

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-119220 (Dokan: AI Powered WooCommerce Multivendor Marketplace Solution <= 5.3.3 - Authorization Bypass via '/dokan/mcp/' Marker in REQUEST_URI), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-119220 (entry last updated 2026-11-18):
Affected:
- dokaninc Dokan: AI Powered WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy: through 5.3.3
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-119220 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-119220 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/763f48c1-9686-4385-a78e-573d4bf2bae6?source=cve
- https://plugins.trac.wordpress.org/browser/dokan-lite/tags/5.3.0/includes/Abilities/Support/RequestContext.php#L223
- https://plugins.trac.wordpress.org/browser/dokan-lite/tags/5.3.0/includes/Abilities/Support/RequestContext.php#L94
- https://plugins.trac.wordpress.org/browser/dokan-lite/tags/5.3.0/includes/Abilities/ProductAbilityScope.php#L179
- https://plugins.trac.wordpress.org/browser/dokan-lite/tags/5.3.0/includes/Abilities/ProductAbilityScope.php#L150
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3785932%40dokan-lite&new=3785932%40dokan-lite
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-119220
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-119220"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • dokaninc Dokan: AI Powered WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy

    through 5.3.3

Evidence 8

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-119220

Is CVE-2026-119220 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-119220?

Dokan: AI Powered WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy: through 5.3.3.Source: cve.now feed data

More CVEs