Skip to main content

Dokan Multivendor EUVDEUVD-2026-52184

| CVE-2026-16564 MEDIUM
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-08-03 WPScan GHSA-rgp2-2vg6-97f5
4.3
CVSS 3.1 · Vendor: WPScan
Share

Severity by source

Vendor (WPScan) PRIMARY
4.3 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
vuln.today AI
4.3 MEDIUM

REST endpoint is network-accessible; vendor account required (PR:L); impact is solely order-status integrity modification with no data exposure or availability loss.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

Lifecycle Timeline

5
Analysis Generated
Aug 03, 2026 - 18:31 vuln.today
CVSS changed
Aug 03, 2026 - 18:22 NVD
4.3 (MEDIUM)
Patch available
Aug 03, 2026 - 07:01 EUVD
CVE Published
Aug 03, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Aug 03, 2026 - 06:00 cve.org
MEDIUM 4.3

DescriptionCVE.org

The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution WordPress plugin before 5.0.9 does not verify order ownership on a REST endpoint that performs bulk order-status changes, allowing users with a Dokan vendor account to modify the status of any WooCommerce order on the marketplace, including orders belonging to other vendors and the store's own customers.

AnalysisAI

Order ownership bypass in Dokan Multivendor for WordPress (versions before 5.0.9) allows any authenticated vendor to modify the status of arbitrary WooCommerce orders across the entire marketplace, including orders owned by other vendors and customers. The flaw stems from a REST endpoint handling bulk order-status changes that accepts attacker-supplied order IDs without verifying the requesting vendor's ownership of those orders. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Register or obtain vendor account
Delivery
Enumerate order IDs from marketplace activity
Exploit
Craft bulk status-change REST request with victim order IDs
Execution
Submit request without ownership check
Persist
Manipulate competitor or customer order statuses
Impact
Disrupt marketplace operations

Vulnerability AssessmentAI

Exploitation Exploitation requires a valid Dokan vendor account on the target WordPress/WooCommerce marketplace (PR:L per CVSS). … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The CVSS 3.1 score of 4.3 (Medium) accurately reflects the constrained impact: the attack is network-accessible with low complexity (AV:N/AC:L), but requires a valid vendor account (PR:L) and yields only a limited integrity impact (I:L) - no data exfiltration is possible (C:N). … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An attacker who holds or registers a vendor account on a vulnerable marketplace enumerates order IDs - which may be predictable sequential integers or discoverable through normal vendor activity - then submits a crafted bulk status-change request to the Dokan REST endpoint referencing those foreign order IDs. A publicly available POC exists demonstrating this technique, meaning the attack requires minimal technical skill. …
Remediation Update the Dokan: AI Powered WooCommerce Multivendor Marketplace Solution plugin to version 5.0.9 or later, which introduces server-side ownership verification on the bulk order-status REST endpoint. … Detailed patch versions, workarounds, and compensating controls in full report.

Threat intelligence, references, and detailed analysis are available after sign-in.

More in Dokan

View all
CVE-2024-3922 CRITICAL POC
10.0 Jun 13

The Dokan Pro plugin for WordPress is vulnerable to SQL Injection via the 'code' parameter in all versions up to, and in

CVE-2022-3915 CRITICAL POC
9.8 Dec 12

The Dokan WordPress plugin before 3.7.6 does not properly sanitise and escape a parameter before using it in a SQL state

CVE-2026-16576 HIGH POC
7.2 Aug 21

Improper access control in the Dokan WooCommerce Multivendor Marketplace WordPress plugin before 5.0.14 enables authenti

CVE-2026-16574 MEDIUM POC
5.4 Aug 08

Dokan's WooCommerce multivendor marketplace WordPress plugin (versions before 5.0.11) exposes a broken object-level auth

CVE-2026-16575 MEDIUM POC
5.3 Aug 21

Unauthenticated information disclosure in Dokan WooCommerce Multivendor Marketplace plugin (versions before 5.0.14) allo

CVE-2026-8761 HIGH
8.8 Aug 05

Privilege escalation in Dokan (WordPress multivendor marketplace plugin) versions up to and including 5.0.1 enables any

CVE-2026-24359 HIGH
8.8 Mar 25

An authentication bypass vulnerability exists in Dokan (Dokan, Inc.) dokan-lite plugin versions through 4.2.4 that allow

CVE-2026-49780 HIGH
8.8 Jun 15

Privilege escalation in Dokan WordPress plugin versions 5.0.2 and earlier allows authenticated low-privileged customer a

CVE-2026-16565 MEDIUM POC
4.3 Aug 03

Broken object-level authorization in the Dokan WordPress plugin (versions before 5.0.9) allows any authenticated vendor

CVE-2020-36748 MEDIUM POC
4.3 Jul 01

The Dokan plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.0.8. Rate

CVE-2023-26525 HIGH
7.1 Dec 20

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in weDevs Dokan - Bes

CVE-2026-57706 HIGH
7.1 Jul 13

Reflected cross-site scripting in the Dokan (dokan-lite) WordPress multivendor marketplace plugin, versions up to and in

Share

EUVD-2026-52184 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy