Improper Authorization (CVE-2026-119220)
Published Last modified Sources: EUVD, CVE.org
- Actively exploited
- Source: VulnCheck KEV (opens in a new tab) How we classify
What is affected, what to do
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.
The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below.
- Affected
- Dokan
lte *..5.3.3
- Dokan
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
7.5
XIEM Effective CVSS
Highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
7.5
CVSS v3
Severity High on the scale from 0 to 10.
Source: EUVD, CVE.org
0.5 %
EPSS score
Low — model estimates < 1% exploitation likelihood.
Source: FIRST EPSS, percentile 45.3
Show all metrics
- Severity
- High
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 83.92 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- actively exploitedSource: VulnCheck KEV (opens in a new tab) How we classify
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 7.5 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 7.5
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 0.5 %
- Low — model estimates < 1% exploitation likelihood.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 45.3
- High — this CVE ranks above the median of all CVEs scored today (rank ≥ 36%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- —
- Published
- CISA assessment (SSVC)
- Exploitation: none known · automatable · Technical impact: partial
- Source: CISA Vulnrichment, as of 18 November 2026
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-285
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
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.
Source: ENISA EUVD, cvelistv5, NVD (NIST), CVE.org (MITRE)
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| dokaninc | Dokan: AI Powered WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy |
|
|
Vendors and products
Weakness classes (CWE)
CWE-285Improper Authorization
Class
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
Entry at MITRE CWE-285
References & sources
- wordfence.comthreat-intel/vulnerabilities/id/763f48c1-9686-4385-a78e-573d4bf…euvd
- plugins.trac.wordpress.orgbrowser/dokan-lite/tags/5.3.0/includes/Abilities/Support/Reques…euvd
- plugins.trac.wordpress.orgbrowser/dokan-lite/tags/5.3.0/includes/Abilities/Support/Reques…euvd
- plugins.trac.wordpress.orgbrowser/dokan-lite/tags/5.3.0/includes/Abilities/ProductAbility…euvd
- plugins.trac.wordpress.orgbrowser/dokan-lite/tags/5.3.0/includes/Abilities/ProductAbility…euvd
- plugins.trac.wordpress.orgchangeset?reponame=&old=3785932@dokan-lite&new=3785932@dokan-li…euvd
- NVD (NIST)vuln/detail/CVE-2026-119220euvd
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: none known, automatable: yes
Show the original change
Individual changes of this event as published by NVD Type Action Before After SSVC assessment added —{"id":"CVE-2026-119220","role":"CISA Coordinator","options":[{"exploitation":"none"},{"automatable":"yes"},{"technicalImpact":"partial"}],"version":"2.0.3","timestamp":"2026-11-18T15:24:57.438096Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
ReceivedWordfence
CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weakness type: CWE-285
Description added or changed
New references:- https://plugins.trac.wordpress.org/browser/dokan-lite/tags/5.3.0/includes/Abilities/ProductAbilityScope.php#L150
- 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/Support/RequestContext.php#L223
- https://plugins.trac.wordpress.org/browser/dokan-lite/tags/5.3.0/includes/Abilities/Support/RequestContext.php#L94
and 2 more references
Show 10 original changes
Individual changes of this event as published by NVD Type Action Before After Description added —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.CVSS added —AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NWeakness type (CWE) added —CWE-285Affected versions (publisher) added —New affected value received. <a href="https://github.com/CVEProject/cvelistV5/blob/main/cves/2026/119xxx/CVE-2026-119220.json">CVE-2026-119220</a>Reference added —https://plugins.trac.wordpress.org/browser/dokan-lite/tags/5.3.0/includes/Abilities/ProductAbilityScope.php#L150Reference added —https://plugins.trac.wordpress.org/browser/dokan-lite/tags/5.3.0/includes/Abilities/ProductAbilityScope.php#L179Reference added —https://plugins.trac.wordpress.org/browser/dokan-lite/tags/5.3.0/includes/Abilities/Support/RequestContext.php#L223Reference added —https://plugins.trac.wordpress.org/browser/dokan-lite/tags/5.3.0/includes/Abilities/Support/RequestContext.php#L94Reference added —https://plugins.trac.wordpress.org/changeset?reponame=&old=3785932%40dokan-lite&new=3785932%40dokan-liteReference added —https://www.wordfence.com/threat-intel/vulnerabilities/id/763f48c1-9686-4385-a78e-573d4bf2bae6?source=cveSource identifier: security@wordfence.com
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2026-119220"><img src="https://intel.neosec.eu/badge/cve/CVE-2026-119220.svg?lang=en" alt="CVE-2026-119220 – NEOSEC Intel" height="20"></a>