CVE-2026-11783
MediumCVSS 6.4Exploitation Probability (EPSS)
Low risk12th percentile - higher than 12% of all known CVEs
Summary
The Dokan plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the Product SKU field in all versions up to and including 5.0.4 due to insufficient input sanitization and output escaping. This allows authenticated attackers with custom-level access or higher to inject arbitrary web scripts that execute when users access affected pages.
Risk Assessment
The risk is that the malicious payload is delivered to site visitors, including unauthenticated users, when the store search widget inserts unescaped AJAX response HTML into the DOM via jQuery's .html() method. This can lead to session theft, redirects to malicious sites, or theft of sensitive data.
Recommendation
It is recommended to immediately update the Dokan plugin to the latest available version that includes a security fix. Additionally, restrict custom-level user permissions and regularly audit roles and plugin capabilities.
Other vulnerabilities in Dokan
See all- CVE-2026-16577Low
The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution WordPress plugin before 5.0.14 does not validate a client-supplied payment amount against the vendor's actual outstanding balance when recording a reverse-withdrawal payment, allowing a vendor to credit their reverse-withdrawal ledger with an arbitrary amount and clear their real commission debt without paying.
- CVE-2026-16576High
The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution WordPress plugin before 5.0.14 does not correctly check user capabilities on some of its admin REST API routes, checking only for a WooCommerce management capability instead of the plugin-installation capability, allowing users such as Shop Managers to install and activate arbitrary plugins from WordPress.org.
- CVE-2026-16575Medium
The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution WordPress plugin before 5.0.14 does not restrict access to per-vendor commission configuration returned by one of its unauthenticated store REST endpoints, allowing any unauthenticated user to disclose a vendor's commission type and, when category-based commission is configured, the per-category and default commission rates.
- CVE-2026-66699Medium
A Broken Access Control vulnerability from a custom role in the Dokan plugin (versions up to 5.0.10) allows a user with a custom role to gain access to functions or data they should not have permission to.
- CVE-2026-8761High
The Dokan plugin for WordPress up to version 5.0.1 is vulnerable to Privilege Escalation due to a missing authorization check in the `CustomersController` REST controller. It 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. Authenticated attackers with Vendor/Seller-level access or above can 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-57706High
The Dokan plugin for WordPress is vulnerable to Reflected Cross-Site Scripting (XSS) due to improper input neutralization during page generation. This affects versions up to and including 5.0.6.
- CVE-2026-11987Medium
The Dokan plugin for WordPress up to version 5.0.4 is vulnerable to Insecure Direct Object Reference (IDOR) via the 'id' parameter. Authenticated attackers with subscriber-level access can read other vendors' products, including unpublished drafts and pending listings.
- CVE-2026-49780High
Dokan versions up to 5.0.2 contain a vulnerability that allows customer privilege escalation.
Original NVD description (English source)
The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Product SKU in all versions up to, and including, 5.0.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with custom-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The malicious payload is delivered to site visitors — including unauthenticated users — when the store search widget inserts the unescaped AJAX response HTML into the DOM via jQuery's .html() method.