Vulnerability in Dokan (WordPress plugin) (CVE-2026-8761)
Summary
Vulnerability in Dokan (WordPress plugin) (CVE-2026-8761). Successful exploitation can lead to full system takeover. Exploitable via CustomersController.
Original description
The description as published by the source.
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.
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-8761 has been found in Dokan (WordPress plugin).
Attackers can target a specific entry point like CustomersController over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Dokan (WordPress plugin) CVE-2026-8761" on the vendor's site.
CVE-2026-8761 (Dokan (WordPress plugin)) — CWE-862 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: CustomersController / manage_woocommerce / GET / PUT
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-862) exists in Dokan (WordPress plugin). Attackers reach the vulnerable code path via CustomersController.
Check the vendor advisory for the affected versions of Dokan (WordPress plugin). Attack surface: CustomersController / manage_woocommerce / GET / PUT.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Dokan (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web nvd.nist.gov
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web security@wordfence.com
- web github.com