Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as marketplace vendor
-
ExploitRequest commission calculation for another vendor's ID
-
ExecutionIDOR bypasses vendor-ownership check
-
ImpactDisclose competitor commission rate and fixed fee
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires an authenticated vendor account on the target Dokan marketplace (the vulnerable commission-calculation feature is only reachable by logged-in vendors), and the affected plugin version must be earlier than 5.2.0. The flaw is a missing ownership check: the attacker simply supplies another vendor's identifier in the commission-calculation request. The primary limiting factor is the authentication requirement - the attacker must obtain a vendor account, though many marketplaces allow self-service vendor registration, which lowers this barrier. No user interaction and no special non-default configuration are required beyond having the multivendor marketplace operational. Impact is limited strictly to disclosure of other vendors' commission rates and fixed fees - no data modification or service disruption. |
| Impact | This is a genuinely low-severity issue and the signals are consistent in pointing that way. The CVSS 3.1 base score of 2.7 (AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N) reflects an authenticated information-disclosure flaw with only a low confidentiality impact and no integrity or availability impact - an IDOR (CWE-200) where one vendor can read the commission rate and fixed fee the administrator set for other vendors. A public exploit exists (WPScan) and a vendor patch is available, but there is no EPSS score, no CISA KEV listing, and no SSVC data in the input, so there is no evidence of active exploitation. POC availability raises the practical likelihood of opportunistic abuse slightly, but POC existence is distinct from active exploitation and should not be conflated with it. One notable divergence: the supplied vector rates privileges as PR:H, yet the affected principal is a marketplace vendor account, which in most Dokan deployments is a low-privilege, often self-registerable role - this likely overstates the privilege barrier (see assessed vector). Net: a real but minor confidentiality leak of business-sensitive pricing data, appropriate for routine patching rather than emergency response. |
| Exploit ScenarioDerived | An attacker registers or already holds a vendor account on a Dokan-powered marketplace, then invokes the commission-calculation functionality while substituting another vendor's identifier. Because the plugin does not verify that the requested vendor matches the requesting vendor, the attacker receives the commission rate and fixed fee the administrator privately configured for that competitor. A public exploit for this issue is available via WPScan, lowering the skill required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 11, 2026
Information disclosure in the Dokan multivendor marketplace plugin for WordPress (versions before 5.2.0) lets any authenticated vendor read the commission rate and fixed fee that the marketplace administrator configured for other vendors, simply by requesting a commission calculation for someone else's vendor identifier. The root cause is a missing ownership check (CWE-200 information exposure) on the commission-calculation feature, which is reachable by a logged-in vendor account - a low barrier on marketplaces that allow self-service vendor registration. Publicly available exploit code exists per the WPScan advisory, no CISA KEV listing has been recorded, and impact is confined to disclosure of pricing configuration: there is no data modification, privilege escalation, or service disruption. The vendor has released a fix in version 5.2.0, and the independent assessment confirms this as a genuinely low-severity issue with a consistent risk picture.
RemediationAI
Vendor-released patch: upgrade the Dokan plugin to version 5.2.0 or later, which closes the missing ownership check in the commission-calculation feature; this is the only complete fix and should be applied across every WordPress instance running the plugin, with staging validation first because Dokan updates can alter commission and vendor-dashboard behavior. Because exploitation requires an authenticated vendor account and the assessed vector is PR:L, the most effective compensating control for sites that cannot patch immediately is to stop untrusted accounts from reaching the vendor dashboard - disable self-service vendor registration, require administrator approval of new vendors, and review existing vendor accounts, then remove or disable any untrusted ones. The trade-off is that this interrupts vendor onboarding and can block legitimate sellers, so it is a temporary measure best paired with a scheduled upgrade. Sites can additionally monitor access logs for repeated commission-calculation requests using vendor identifiers that do not match the authenticated session, and can restrict or temporarily disable the commission-calculation endpoint if it is not needed during the exposure window, though this will impair vendor payout visibility. Consult the WPScan advisory at https://wpscan.com/vulnerability/ddce69ff-5325-432c-9f3a-66ec9a19bcb4/ for the vendor's patched release details; no vendor-released fix is documented for versions prior to 5.2.0, so upgrading is required rather than optional.
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-based multivendor marketplace plugin for WordPress; it adds vendor dashboards, product management, and commission handling on top of WooCommerce. The affected component is the commission-calculation routine, which computes a vendor's payout using a per-vendor commission rate plus a fixed fee set by the marketplace administrator. The flaw is a missing ownership/authorization check: the calculation accepts a vendor identifier supplied by the caller and returns the resulting configuration values without confirming that the requesting user actually owns that vendor record. This is a classic insecure direct object reference pattern that the CVE maps to CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor). The CPE data (cpe:2.3:a:unknown:dokan:_ai_powered_woocommerce_multivendor_marketplace_solution) confirms the target is the Dokan plugin deployed on WordPress, with the EUVD entry specifying the affected range as 0 through versions below 5.2.0. The assessed CVSS vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N reflects network reachability, low attack complexity, a low-privileged authenticated vendor account as the only prerequisite, no user interaction, and a confidentiality-only impact - the PR:L designation means the attacker must already hold a vendor-level account, which is a materially different and lower barrier than the PR:H value in the headline score. No special non-default configuration is needed beyond an operational multivendor marketplace.
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:H/UI:N/S:U/C:L/I:N/A:N
Remotely reachable authenticated endpoint requiring only a vendor-level account (PR:L, not PR:H, as vendors are typically self-registerable low-privilege users); only commission data leaks, so C:L and I/A:N.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution WordPress plugin before 5.2.0 does not verify that the vendor a commission calculation is requested for is the requesting vendor, allowing vendors to disclose the commission rate and fixed fee the marketplace administrator configured for other vendors.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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
Broken object-level authorization in the Dokan WordPress plugin (versions before 5.0.9) allows any authenticated vendor
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
EUVD-2026-96745
GHSA-69ch-m3g4-93cp
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB