Skip to main content

Dokan Pro CVE-2026-12224

| EUVDEUVD-2026-40928 HIGH
Improper Privilege Management (CWE-269)
2026-07-01 Wordfence GHSA-9cv2-mw8g-x6gp
8.8
CVSS 3.1 · Vendor: Wordfence
Share

Severity by source

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

Network REST endpoint (AV:N) reachable by any authenticated vendor (PR:L) with no user interaction; missing capability allowlist yields administrator access and full C/I/A impact.

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

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

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

Lifecycle Timeline

2
Analysis Generated
Jul 01, 2026 - 08:32 vuln.today
CVE Published
Jul 01, 2026 - 06:51 nvd
HIGH 8.8

DescriptionCVE.org

The Dokan Pro plugin for WordPress is vulnerable to privilege escalation via update_capabilities REST Endpoint in all versions up to, and including, 5.0.4. This is due to the update_capabilities() REST handler accepting arbitrary capability strings from the request body and passing them directly to WP_User::add_cap() with no allowlist validation, only verifying that the caller holds the dokandar capability. This makes it possible for authenticated attackers with a self-provisioned Vendor-level access and above, on sites with the Vendor Staff module enabled, to grant arbitrary WordPress capabilities, including administrator, to any vendor_staff account, leading to a full site takeover.

AnalysisAI

Privilege escalation in the Dokan Pro WooCommerce multivendor plugin for WordPress (all versions through 5.0.4) allows an authenticated vendor-level attacker to grant themselves or a controlled vendor_staff account the WordPress administrator capability, resulting in full site takeover. The flaw stems from the update_capabilities() REST handler accepting arbitrary capability strings with no allowlist, only checking for the dokandar capability. No public exploit has been identified at time of analysis, and no EPSS or KEV signals were supplied; however, the issue is reported by Wordfence and exploitation is straightforward on sites where the Vendor Staff module is enabled and vendor self-registration is permitted.

Technical ContextAI

Dokan Pro is the commercial extension of the widely used Dokan multivendor marketplace plugin (vendor weDevs, CPE cpe:2.3:a:wedevs:dokan_pro), which turns a WooCommerce store into a multi-seller marketplace with per-vendor staff accounts. The vulnerability lives in the plugin's REST API layer: the update_capabilities() endpoint reads capability identifiers directly from the request body and passes them to WordPress core's WP_User::add_cap(), which unconditionally attaches any capability string to a user's meta. The only authorization gate is a check that the caller holds the dokandar (vendor) capability, and there is no allowlist restricting which capabilities may be assigned. This is a textbook CWE-269 (Improper Privilege Management) failure - the code trusts client-supplied privilege identifiers and provides no separation between capabilities a vendor may legitimately delegate to staff and high-privilege capabilities such as administrator.

RemediationAI

No vendor-released patched version was identified at time of analysis; the description confirms only that versions through 5.0.4 are vulnerable, so administrators should upgrade to the latest Dokan Pro release above 5.0.4 as soon as weDevs publishes a fix and monitor the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/6ff9c202-b3e8-4660-8763-a9fee468203e?source=cve) and https://dokan.co/ for the exact fixed version. Until a patch is applied, the most effective compensating control is to disable the Vendor Staff module, which removes the vulnerable endpoint entirely at the cost of losing staff-account functionality for vendors. Where the Staff module must stay enabled, temporarily disable open vendor self-registration (require manual admin approval of new vendors) to remove the low-privilege foothold, and restrict or WAF-filter access to the Dokan REST update_capabilities route; audit existing vendor_staff and vendor accounts for any that already hold administrator or other elevated capabilities and revoke them, since a successful attack leaves a persistent privileged account behind.

Share

CVE-2026-12224 vulnerability details – vuln.today

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