Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft URL with XSS payload in Dokan parameter
-
DeliveryDeliver link to admin/vendor victim
-
ExploitVictim clicks, server reflects payload unsanitized
-
ExecutionScript executes in victim browser session
-
ImpactSteal session/perform actions as victim
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires victim interaction: the target must click or otherwise load an attacker-crafted URL carrying the XSS payload in the vulnerable Dokan request parameter (UI:R). No authentication or special privileges are needed on the attacker side (PR:N), and the attack is delivered over the network (AV:N) against sites running dokan-lite <= 5.0.6, but impact is maximized when the victim is an authenticated administrator or vendor. Limiting factors: mandatory user interaction (no automatic/wormable exploitation), the non-persistent reflected nature (payload must be re-delivered to each victim), and the requirement that the site actually runs the vulnerable Dokan plugin version. |
| Impact | Signals are moderate and internally consistent. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L, base 7.1) shows network reach and no privileges but mandatory user interaction (UI:R), which is the key limiting factor - a victim must be lured into clicking a crafted link. The scope change (S:C) and low CIA impacts are typical Patchstack scoring for XSS where script escapes into the browser security context. No EPSS score, KEV entry, or public POC was provided, so there is no evidence of active or automated exploitation; this reads as a real but not urgent web-application flaw rather than a mass-exploited critical. The A:L (availability) rating is unusual for reflected XSS and may be generous - reflected XSS more commonly yields confidentiality/integrity impact only; treat the availability claim with mild skepticism. Overall this is a standard-priority patch-when-available item, elevated somewhat by Dokan's popularity but constrained by the user-interaction requirement. |
| Exploit ScenarioDerived | An attacker crafts a URL to the target WordPress site containing a malicious script payload in a vulnerable Dokan parameter and delivers it via email, chat, or a link on another site. When a logged-in administrator or vendor clicks the link, the reflected script executes in their browser under the site's origin, allowing session token theft, actions performed as the victim, or redirection. No public POC is identified, but reflected XSS in WordPress plugins is well understood and the low attack complexity makes weaponization straightforward. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 13, 2026
Reflected cross-site scripting in the Dokan (dokan-lite) WordPress multivendor marketplace plugin, versions up to and including 5.0.6, lets a remote attacker inject script that executes in a victim's browser when they follow a crafted link. Reported by Patchstack (CWE-79) and rated CVSS 7.1, the scope-changed vector reflects that injected script runs in the user's authenticated WordPress session context. There is no public exploit identified at time of analysis and the flaw is not listed in CISA KEV; exploitation requires the target to click an attacker-supplied URL.
RemediationAI
Upgrade the Dokan plugin to a fixed release newer than 5.0.6; the input data does not specify an exact patched version, so no vendor-released patch version is independently confirmed here - consult the Patchstack advisory (https://patchstack.com/database/Wordpress/Plugin/dokan-lite/vulnerability/wordpress-dokan-plugin-5-0-6-cross-site-scripting-xss-vulnerability) and the plugin's WordPress.org changelog for the corrected version and update immediately. Until a confirmed patch is applied, deploy a Web Application Firewall rule (Patchstack's virtual patch, or WordPress security plugins such as Wordfence) to filter reflected XSS payloads on the affected parameter, which adds latency and can produce false positives on legitimate rich input. As additional compensating controls, set a restrictive Content-Security-Policy header to limit inline script execution (may break themes/plugins that rely on inline JS) and instruct administrators and vendors to avoid clicking untrusted links to the site while unpatched.
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 widely used WordPress plugin that turns a site into a multi-vendor e-commerce marketplace (vendor dashboards, storefronts, product listings). The affected component is identified by CPE cpe:2.3:a:dokan,_inc.:dokan:*:*:*:*:*:*:*:* covering all versions through 5.0.6. The root cause is CWE-79, Improper Neutralization of Input During Web Page Generation: a request parameter is reflected back into an HTML response without proper output encoding or sanitization, so attacker-controlled input is parsed as active markup/JavaScript by the victim's browser. Because it is reflected (non-persistent), the malicious payload travels in the request itself rather than being stored server-side.
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:N/UI:R/S:C/C:L/I:L/A:L
Reflected XSS is network-delivered with low complexity and no privileges but needs victim clicks (UI:R); script escaping into browser context gives S:C with low C/I, and availability impact does not realistically apply (A:N).
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Dokan, Inc. Dokan dokan-lite allows Reflected XSS.This issue affects Dokan: from n/a through <= 5.0.6.
Executive ViewAI
The Dokan WordPress multivendor plugin (versions ≤5.0.6) contains a reflected XSS vulnerability enabling attackers to execute malicious scripts in users' browsers through crafted links, potentially compromising vendor and customer accounts. With no available patch, organizations require immediate mitigation.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable the Dokan plugin if operationally feasible; (2) Implement Web Application Firewall rules to block script injection attempts targeting Dokan endpoints; (3) Enforce Content Security Policy (CSP) headers restricting inline script execution; (4) Restrict vendor dashboard and administrator access to known IP ranges; (5) Enable comprehensive WordPress audit logging and monitor for suspicious user sessions and unauthorized account activities.
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
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
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
Privilege escalation in Dokan WordPress plugin versions 5.0.2 and earlier allows authenticated low-privileged customer a
An authentication bypass vulnerability exists in Dokan (Dokan, Inc.) dokan-lite plugin versions through 4.2.4 that allow
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-43361
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB