Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or obtain Dokan vendor account
-
DeliveryEnumerate target vendor's product IDs via public store listings
-
ExploitCraft REST API write request with victim product ID
-
ExecutionSubmit request to Dokan product-attribute endpoint
-
ImpactServer applies unauthorized attribute changes to victim product
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
|
| Exploitation Conditions | Exploitation requires the attacker to hold an active Dokan vendor account (authenticated, low-privilege - PR:L per CVSS) on the target marketplace instance. The vulnerable code path is specifically the product-attribute and default-attribute REST write endpoints exposed by the Dokan plugin; the plugin must be installed and active on a WooCommerce site running a version prior to 5.0.9. No special server-side configuration beyond a standard Dokan installation is needed. Exploitation is limited by the vendor account prerequisite - unauthenticated or subscriber-level users cannot exploit this flaw. Marketplaces with open or free vendor registration are at elevated risk since the barrier to obtaining the required privilege level is minimal. |
| Impact | The NVD CVSS 3.1 score of 4.3 (Medium) with vector AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N accurately reflects the bounded impact: network-reachable, low complexity, but gated behind a vendor account (PR:L), with only integrity impact and no data exfiltration or denial-of-service potential. The EPSS score of 0.13% at the 3rd percentile suggests very low observed exploitation pressure despite the availability of a public PoC, likely because the attack surface requires an active vendor registration on each targeted marketplace instance. No CISA KEV listing confirms no mass exploitation detected at time of analysis. The realistic risk is highest for marketplaces with open or low-barrier vendor registration, where a malicious actor could self-register and immediately abuse the endpoint to tamper with competitor product listings - a meaningful business integrity risk even if technical severity is moderate. No signal conflicts between CVSS, EPSS, and KEV status are present. |
| Exploit ScenarioDerived | An attacker registers or already holds a vendor account on a target Dokan-powered WooCommerce marketplace. Using the publicly available PoC from WPScan, the attacker sends a crafted REST API PATCH or PUT request to the product-attribute write endpoint, substituting a competitor's product ID in place of their own. The server applies the attribute changes without verifying ownership, allowing the attacker to corrupt or manipulate a competitor's product variants, potentially degrading listing quality or causing incorrect product options to appear to buyers. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 03, 2026
Broken object-level authorization in the Dokan WordPress plugin (versions before 5.0.9) allows any authenticated vendor on a multivendor marketplace to overwrite product attributes and default attributes belonging to other vendors via the plugin's REST API write endpoints. Exploitation requires only a low-privilege vendor account - no admin access needed - making this accessible to any registered seller on the platform. A publicly available proof-of-concept exists per WPScan, though EPSS sits at 0.13% (3rd percentile), indicating limited observed exploitation activity so far; the vulnerability is not listed in CISA KEV.
RemediationAI
Upgrade the Dokan plugin to version 5.0.9 or later, which introduces ownership verification on the product-attribute REST write endpoints. The patch is available from the vendor and should be applied immediately via the WordPress plugin update mechanism or by downloading directly from the plugin repository. If immediate patching is not possible, site administrators should consider restricting vendor REST API access at the web server or WAF layer by blocking write requests to the Dokan product-attribute REST routes (e.g., paths matching /wp-json/dokan/*/products/*/attributes) for all but trusted IP ranges - though this may disrupt legitimate vendor operations. Alternatively, temporarily suspending open vendor registration to limit the attacker pool reduces exploitation surface until the patch is applied. Neither workaround eliminates the underlying flaw, and patching to 5.0.9 remains the definitive fix.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Dokan is a WooCommerce extension that converts a standard WordPress e-commerce store into a multivendor marketplace, where independent vendors manage their own product listings. The plugin exposes REST API write endpoints for managing WooCommerce product attributes (taxonomies used for variants such as size, color, etc.) and default attribute assignments. CWE-639 (Authorization Bypass Through User-Controlled Key) is the root cause: the endpoint accepts a product or attribute ID supplied by the caller but fails to validate that the authenticated vendor actually owns the referenced product before applying changes. An attacker can substitute a product ID belonging to a different vendor and the server will process the modification without ownership verification. The affected CPE is cpe:2.3:a:unknown:dokan:_ai_powered_woocommerce_multivendor_marketplace_solution:*:*:*:*:*:*:*:* covering all versions up to but not including 5.0.9.
Know when Dokan gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Network-reachable REST endpoint (AV:N), trivial to exploit once authenticated (AC:L), vendor account required (PR:L), no confidentiality or availability impact - only product attribute integrity is affected.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution WordPress plugin before 5.0.9 does not verify product ownership on its product-attribute REST write endpoints, allowing users with a Dokan vendor account to modify the product attributes and default attributes of any other vendor's products on the marketplace.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
The Dokan Pro plugin for WordPress is vulnerable to SQL Injection via the 'code' parameter in all versions up to, and in
The Dokan WordPress plugin before 3.7.6 does not properly sanitise and escape a parameter before using it in a SQL state
Improper access control in the Dokan WooCommerce Multivendor Marketplace WordPress plugin before 5.0.14 enables authenti
Dokan's WooCommerce multivendor marketplace WordPress plugin (versions before 5.0.11) exposes a broken object-level auth
Unauthenticated information disclosure in Dokan WooCommerce Multivendor Marketplace plugin (versions before 5.0.14) allo
Unauthenticated privilege escalation in the Blocksy Companion WordPress plugin (versions up to and including 2.1.58) all
Privilege escalation in Dokan (WordPress multivendor marketplace plugin) versions up to and including 5.0.1 enables any
An authentication bypass vulnerability exists in Dokan (Dokan, Inc.) dokan-lite plugin versions through 4.2.4 that allow
Privilege escalation in Dokan WordPress plugin versions 5.0.2 and earlier allows authenticated low-privileged customer a
Order ownership bypass in Dokan Multivendor for WordPress (versions before 5.0.9) allows any authenticated vendor to mod
The Dokan plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.0.8. Rate
PHP Object Injection in the Dokan Pro WordPress plugin (versions 5.0.2 and earlier) allows an authenticated user holding
EUVD-2026-52185
GHSA-cjjh-8xvm-fchv
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB