sales@hackhalt.com

Home / Threats / CVE-2026-8761

Dokan - Privilege Escalation (CVE-2026-8761)

CVE-2026-8761

Vulnerability CVE-2026-8761 PLUGIN dokan HIGH

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.

CVE-2026-8761

HIGH CVSS 8.8 Published 2026-08-05 Updated 2026-08-12
AI Risk Critical (92/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P1 Immediate
Severity Band HIGH
CVSS Vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected Components 2
Reference Links 10
AI Risk Engine Critical (92/100)
Exploitability Very High
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-08-05 CVE published and first recorded in the threat feed.
  2. 2026-08-12 Record updated with latest vulnerability metadata.
  3. 2026-08-07 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 45 days ago

AI enriched 45 days ago (2026-08-07 19:51 UTC)

Technical Summary

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,…

Potential Impact

Severity is HIGH (CVSS 8.8). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Very High based on remote code execution potential, low-bar exploit prerequisites.

Primary risk drivers: remote code execution potential, low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 92/100 (Critical, Very High) with priority P1 Immediate. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Affected Products

Dokan PLUGIN · dokan Affected range not specified Fixed version not specified
Dokan Lite PLUGIN · dokan-lite Affected range not specified Fixed version not specified

References

What to do about this

Patch promptly The consequence is significant even where an attacker needs a foothold first.

Fix it

Update Dokan to the latest available version.

Where the vendor has not published a fix yet, disable the plugin until they do.

Cannot update today? Unauthorised administrator detection in Hack Halt ProSecure blocks this class of attack before WordPress processes the request.

Alert when a new administrator appears or a role is escalated. Creating a hidden admin is the most common persistence step after a WordPress compromise.

Compare Hack Halt plans Start free

Not sure if you are affected?

Scan your site to see whether it runs Dokan, and at which version.

Free, no installation, no account. It reads what your site already publishes, then tells you which plugins carry known vulnerabilities and what to do about each one.

Scan my site free See what Hack Halt does

Am I affected by this vulnerability?

You are affected if your site runs Dokan.

How do I fix it?

Update Dokan to the latest available version. Where the vendor has not yet published a fix, remove or disable the plugin until they do. Until you can update, Unauthorised administrator detection in Hack Halt ProSecure contains this class of attack at the request layer.

What can an attacker actually do?

This is a Privilege Escalation flaw. An attacker who exploits it can raise a low-privilege account, or none at all, to administrator.