Skip to main content

Dokan Pro CVE-2026-65494

| EUVDEUVD-2026-48105 HIGH
SQL Injection (CWE-89)
2026-07-23 Patchstack GHSA-vrgp-j4x4-3mqv
7.1
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Register free Subscriber account
  2. Delivery
    Authenticate to marketplace
  3. Exploit
    Send crafted SQL payload to Dokan Pro endpoint
  4. Execution
    Trigger blind SQL injection
  5. Impact
    Exfiltrate database records and password hashes

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Persistence

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 low-privilege WordPress account at Subscriber level or above (CVSS PR:L), obtainable through the site's registration flow - which on marketplace deployments is frequently open by default, lowering the barrier. Beyond a valid account, the attacker needs network access to the vulnerable Dokan Pro request handler and no user interaction (UI:N). Limiting factors: the high attack complexity (AC:H) indicates the injection is not trivially triggerable and likely demands crafted or blind payloads, and sites that disable open registration or require manual account approval remove the prerequisite foothold entirely. The specific vulnerable parameter/endpoint is not disclosed in the provided data and should be confirmed from the Patchstack advisory.

Impact

The CVSS 3.1 vector CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:L yields 7.1 (High): network-reachable and requiring no user interaction, but with high attack complexity and low-privilege authentication (PR:L). The PR:L requirement is meaningful - on many WordPress marketplaces registration is open, so obtaining a Subscriber account is often trivial, which partially offsets the AC:H rating. Impact is weighted toward confidentiality (C:H) with a scope change (S:C), consistent with reading data outside the plugin's authorization context; integrity is unaffected (I:N) and availability impact is limited (A:L). EPSS and KEV data were not provided in the intelligence set, so exploitation probability cannot be quantified and there is no evidence of active exploitation. No POC was supplied. Overall this is a credible priority for any live multivendor Dokan Pro store with open registration, but the absence of KEV/EPSS/POC signals suggests it is not yet under mass exploitation - patch on a normal-to-expedited cycle.

Exploit ScenarioDerived

An attacker registers a free Subscriber (or vendor) account on a Dokan Pro-powered marketplace with open registration, then sends crafted requests to the vulnerable plugin endpoint embedding SQL payloads in a parameter. Exploiting the injection over the network (AV:N) without any user interaction, they enumerate and exfiltrate database contents beyond their authorization scope, including customer records and WordPress user password hashes. No public POC was provided, and the high attack complexity (AC:H) implies the payload requires some tailoring, such as a blind/time-based technique.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 23, 2026

Authenticated SQL injection in the Dokan Pro WordPress multivendor marketplace plugin (versions <= 5.0.2) allows a low-privileged Subscriber-level user to inject malicious SQL into backend database queries, enabling extraction of sensitive data across the WordPress store. Reported by Patchstack and rated CVSS 7.1, the scope-changed vector reflects that a compromised low-tier account can reach data beyond its own authorization boundary. No public exploit identified at time of analysis, and it is not listed in CISA KEV.

RemediationAI

Upgrade Dokan Pro to a version later than 5.0.2 (the next maintenance release above 5.0.2); the exact fixed version is not stated in the provided intelligence, so consult the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/dokan-pro/vulnerability/wordpress-dokan-pro-plugin-5-0-2-sql-injection-vulnerability?_s_id=cve) and the WeDevs/Dokan changelog to confirm the patched build before deploying. Until patched, reduce exposure by disabling open self-registration or gating new Subscriber/vendor accounts behind manual approval to remove the low-privileged foothold the exploit needs (side effect: adds friction to legitimate vendor onboarding). Deploy a WAF or the Patchstack virtual patch with a rule targeting the vulnerable endpoint to block SQL metacharacters (side effect: possible false positives on legitimate store queries), and restrict or monitor access to the affected Dokan Pro request path. Because this is a data-confidentiality issue, also rotate WordPress secrets and, if compromise is suspected, force password resets since wp_users hashes may have been exposed.

Affected VersionsENISA

Dokan Pro n/a ≤5.0.2

Affected Packages

euvd dokan_pro no fix

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 Pro is the commercial extension of the widely used Dokan multivendor marketplace plugin for WordPress/WooCommerce, adding vendor storefronts, subscriptions, and reporting features. The root cause is CWE-89 (Improper Neutralization of Special Elements used in an SQL Command): user-controllable input reaching a database query is concatenated without adequate parameterization or sanitization via WordPress's $wpdb prepared-statement API. The affected component is identified by CPE cpe:2.3:a:dokan:dokan_pro (all versions through 5.0.2). Because WordPress plugins share a single database with the core CMS, an injection point in a plugin query can expose core tables (e.g., wp_users, wp_usermeta) containing password hashes and session/auth data.

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

Vendor (Patchstack) PRIMARY 7.1 HIGH
AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:L
vuln.today AI 7.1 HIGH

Network SQLi reachable by any low-privilege Subscriber (PR:L), blind/complex injection (AC:H); scope change and cross-table read give S:C and C:H with no integrity impact.

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

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
Low

DescriptionCVE.org

Subscriber SQL Injection in Dokan Pro <= 5.0.2 versions.

Executive ViewAI

Why It Matters

Dokan Pro marketplace software (versions 5.0.2 and earlier) contains a vulnerability allowing lower-level user accounts to access confidential data across the entire WordPress marketplace, including customer information and vendor details. Exploitation requires account access but could be leveraged by employees, partners, or compromised low-tier accounts to exfiltrate sensitive business and customer data. Organizations using affected versions face immediate data breach risk, customer notification obligations, and potential regulatory penalties.

Business Impact: High
Compensating Controls

Implement database-level privilege restrictions limiting the WordPress database user to only required tables and minimal operations; deploy web application firewall (WAF) rules to detect and block SQL injection patterns targeting Dokan Pro input fields; restrict or disable Subscriber-level user registrations until a patch is available; maintain comprehensive database query logging with real-time alerts for anomalous data access from low-privilege accounts; establish daily monitoring of vendor security channels for emergency patches or workarounds.

Threat Intelligence Overview

EPSS Score
0.3%
Top 81% exploitable
Prevalence
Medium
popular WordPress multivendor plugin, but paid Pro tier limits install base
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Partial

Priority Score

36
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +36
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

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-107645 CRITICAL
9.1 Oct 10

Unauthenticated privilege escalation in the Blocksy Companion WordPress plugin (versions up to and including 2.1.58) all

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-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-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-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-2026-16564 MEDIUM POC
4.3 Aug 03

Order ownership bypass in Dokan Multivendor for WordPress (versions before 5.0.9) allows any authenticated vendor to mod

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

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