Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running Dokan ≤5.3.2
-
ExploitSend request to unprotected endpoint
-
ExecutionBypass missing authorization check
-
ImpactRead access-controlled data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The available sources do not name the specific endpoint, feature, or configuration involved; the description only states a missing-authorization flaw in Dokan 'Incorrectly Configured Access Control Security Levels,' so the precise trigger is not described in the available sources. Per the CVSS vector (PR:N/UI:N/AC:L), exploitation requires no authentication, no user interaction, and low complexity, meaning it is reachable against a default network-exposed installation. The main limiting factor is impact scope: only low confidentiality (C:L, no integrity or availability), and exploitation is bounded to sites running an affected Dokan version (through 5.3.2). |
| Impact | This is a moderate, not emergency-grade, issue despite its network-facing CVSS vector. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N, base 5.3) indicates a remotely reachable, low-complexity flaw requiring no privileges or user interaction, but the impact is narrow: low confidentiality only, with no integrity or availability effect (C:L/I:N/A:N). This pattern - a missing-authorization/broken-access-control bug reported by Patchstack - typically maps to unauthorized read access to data that should be access-controlled, consistent with CWE-862. No EPSS score was provided in the input, so exploitation probability cannot be quantified here. The vulnerability is NOT on the CISA KEV list and there is no SSVC-style exploitation signal beyond the vuln.today 'this_month' priority label, which aligns with a 'patch on a normal cycle' posture rather than act_now/emergency. The single reference is a Patchstack database entry describing the vulnerability, not verified working exploit code, so active or public exploitation is not established. Net: a genuine but limited-impact information-exposure issue in a popular WordPress plugin - worth remediating on a routine monthly cadence, not a drop-everything event. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends a request to a Dokan-powered WordPress site targeting a plugin endpoint whose authorization check is missing or misconfigured, and retrieves data that should have been access-restricted. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, no login, user interaction, or special timing is needed, but impact is limited to confidentiality (C:L) - no data modification or service disruption. No public exploit code was identified in the provided sources; only a Patchstack vulnerability database reference exists. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Nov 03, 2026
Missing authorization in the Dokan Lite WordPress plugin through 5.3.2 permits unauthenticated network attackers to access limited information guarded by incorrectly configured access controls, with low confidentiality impact and no integrity or availability effect. No public exploit is identified at time of analysis, and active exploitation is not confirmed in the supplied data.
RemediationAI
No fixed version is listed in the supplied data; monitor the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/dokan-lite/vulnerability/wordpress-dokan-plugin-5-3-2-broken-access-control-vulnerability?_s_id=cve and update Dokan Lite beyond 5.3.2 when the vendor publishes a patched release, which is the complete fix. If Dokan Lite cannot be updated, disabling the plugin removes the exposure but eliminates its multivendor marketplace functionality; restricting access to the plugin at the web server or WAF layer can reduce exposure, but because the vulnerable endpoint is not identified, such restrictions must be broad and may block legitimate marketplace traffic.
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
The flaw is a missing authorization issue (CWE-862) affecting the Dokan Lite WordPress plugin, with CPE cpe:2.3:a:wedevs:dokan:*:*:*:*:*:*:*:* and an upper affected bound of 5.3.2. The source does not name the endpoint, feature, or configuration that lacks the authorization check, so the trigger is not described in the available sources. The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N indicates network reachability without authentication or user interaction and limits impact to low confidentiality disclosure.
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:N/S:U/C:L/I:N/A:N
Missing authorization is remotely reachable with no auth or interaction (AV:N/AC:L/PR:N/UI:N); impact is limited to unauthorized data read, so C:L and I:N/A:N.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Missing Authorization vulnerability in weDevs Dokan dokan-lite allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Dokan: from n/a through 5.3.2.
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
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-116089
NVD
CVE.org
Vulnrichment
GitHub PoC
Exploit-DB