WordPress Dokan Plugin Privilege Escalation via REST API

The Dokan plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 5.0.1. This is due to a missing authorization check in the `CustomersController` REST controller (`includes/REST/CustomersController.php`), which re-registers WooCommerce's customer CRUD routes under the `/dokan/v1/customers/` namespace and replaces WooCommerce's native `manage_woocommerce` capability check with a vendor-only check that inspects the **requesting** user's role and never validates the **target** user. This makes it possible for authenticated attackers with Vendor/Seller-level access and above to read, modify, or delete any WordPress user — including administrators — via `GET`/`PUT`/`DELETE` requests against `/wp-json/dokan/v1/customers/{id}`. Setting the `password` parameter on an administrator's record yields a full site takeover.

Casky was already ahead

This CVE exploits attack patterns that Casky's 283matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

The Dokan plugin for WordPress contains a critical privilege escalation vulnerability in its REST API implementation. The CustomersController fails to properly validate authorization when re-registering WooCommerce customer endpoints under the /dokan/v1/ namespace, replacing WooCommerce's native capability checks with insufficient vendor-only checks. This vulnerability affects all versions up to 5.0.1 and allows authenticated attackers with minimal privileges to escalate their access by exploiting the flawed authorization logic. Any WordPress installation using Dokan becomes a target, particularly multi-vendor marketplaces where customer data sensitivity is high.

Casky's 283 mapped skills detect the attack patterns underpinning this vulnerability by analyzing authorization bypass chains across MITRE ATT&CK's Access Control and Privilege Escalation tactics (TA0004, TA0006). Practitioners using Casky would identify findings related to improper input validation (CWE-862), suspicious REST API calls to /dokan/v1/customers endpoints with insufficient permission checks, and role verification failures in request handlers. Extended reasoning through Claude AI helps practitioners correlate multiple detection points—such as authentication context mismatches, capability check bypasses, and unexpected customer data access patterns—to confirm privilege escalation attempts. The skill set reveals both the vulnerable code path and the attacker's progression from initial access to elevated permissions, enabling rapid incident response and remediation.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

283 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-8761.

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

Access with Stolen Session Cookie

cryptography · low

Run

MITRE ATT&CK Techniques

TA0004 TA0006

Investigate the attack patterns behind CVE-2026-8761

Casky has 283 skills that investigate the attack patterns behind CVE-2026-8761. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn