Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Network AJAX endpoint, low complexity, vendor account required (PR:L); no confidentiality loss or availability impact confirmed; integrity impact is low per CVSS granularity despite broad order manipulation scope.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
Lifecycle Timeline
3DescriptionCVE.org
The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution - Build Your Own Amazon, eBay, Etsy plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.0.3 via the change_order_status, add_order_note, delete_order_note, add_shipping_tracking_info, grant_access_to_download, and revoke_access_to_download AJAX handlers due to missing ownership validation on a user-controlled order ID key. This makes it possible for authenticated attackers, with custom vendor-level access and above, to modify the status of arbitrary orders, add attacker-controlled notes to any order (including customer-facing notes that trigger WooCommerce notification emails to buyers), delete any order note or WordPress comment by ID regardless of ownership, inject fake shipping tracking information on any order, and grant or revoke downloadable-product permissions on any order in the marketplace. Critically, nonce validity is not a barrier to exploitation: each of these AJAX handlers generates and embeds its nonce on the authenticated vendor's own dashboard order pages (e.g., /dashboard/orders/?order_id=OWN_ORDER_ID), which the attacker legitimately controls. The attacker harvests a valid nonce from their own order detail page and replays it against a victim order ID - the nonce only proves the request originates from a logged-in session, not that the order belongs to that vendor. This directly rebuts the prior rejection reasoning that 'users cannot generate valid nonces on command': vendor users can and do generate valid nonces on demand simply by loading their own dashboard pages. Source-code analysis confirmed the vulnerable code path is present and unpatched through version 5.0.1.
AnalysisAI
Insecure Direct Object Reference across six AJAX handlers in the Dokan multivendor marketplace plugin for WordPress allows authenticated vendor-level users to manipulate arbitrary marketplace orders they do not own, in all versions up to and including 5.0.3. Affected operations include changing order status, injecting customer-facing notes that trigger WooCommerce notification emails to buyers, deleting any order note or WordPress comment by raw ID, inserting fraudulent shipping tracking data, and granting or revoking downloadable product access on any order in the installation. The nonce-based CSRF protection provides no ownership barrier because vendors legitimately generate valid nonces from their own dashboard pages and can replay them against any order ID - no public exploit identified at time of analysis, though vulnerable code paths are confirmed in source at version 5.0.1 by Wordfence.
Technical ContextAI
The vulnerability is classified as CWE-639 (Authorization Through User-Controlled Key): the Dokan plugin's PHP Ajax class (includes/Ajax.php) accepts a POST-supplied order_id, validates a WordPress nonce, and then acts on the referenced order without verifying that the requesting vendor is the owner of that order. WordPress nonces are session-scoped anti-CSRF tokens - they authenticate the session, not the resource being accessed. The six vulnerable handlers (grant_access_to_download at L225/L293, change_order_status at L302, revoke_access_to_download at L387/L404, add_order_note at L412/L438, add_shipping_tracking_info at L455/L485, delete_order_note at L522/L556) all share this pattern. The delete_order_note handler additionally accepted any integer comment ID, enabling deletion of arbitrary WordPress comments beyond WooCommerce order notes. The fix, confirmed in GitHub PR #3246, adds dokan_is_seller_has_order() ownership verification before every handler and introduces comment_type validation in delete_order_note to restrict deletions to genuine 'order_note' comments. The affected CPE is cpe:2.3:a:dokaninc:dokan covering the dokan-lite WordPress plugin.
RemediationAI
The upstream fix is confirmed via GitHub Pull Request #3246 (https://github.com/getdokan/dokan/pull/3246) and a corresponding WordPress.org changeset 3564542 (https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3564542%40dokan-lite&new=3564542%40dokan-lite). The fix adds dokan_is_seller_has_order() ownership checks before all six AJAX handlers and restricts delete_order_note to comment_type 'order_note' only. Upstream fix available (PR/commit); released patched version not independently confirmed - site administrators should monitor the WordPress.org plugin page for a release above 5.0.3 incorporating these changes and apply it immediately. As an interim compensating control, restrict vendor registration to vetted, trusted parties to raise the practical barrier to exploitation (the PR:L requirement means an attacker must hold a valid vendor account). Disabling the affected AJAX actions is not viable without breaking vendor dashboard functionality. Monitor the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/998e545c-2ad5-48ec-bad1-d346170af408) for confirmed patch version and WAF rule availability.
The Dokan Pro plugin for WordPress is vulnerable to SQL Injection via the 'code' parameter in all versions up to, and in
The Dokan WordPress plugin before 3.7.6 does not properly sanitise and escape a parameter before using it in a SQL state
Improper access control in the Dokan WooCommerce Multivendor Marketplace WordPress plugin before 5.0.14 enables authenti
Dokan's WooCommerce multivendor marketplace WordPress plugin (versions before 5.0.11) exposes a broken object-level auth
Unauthenticated information disclosure in Dokan WooCommerce Multivendor Marketplace plugin (versions before 5.0.14) allo
Privilege escalation in Dokan (WordPress multivendor marketplace plugin) versions up to and including 5.0.1 enables any
An authentication bypass vulnerability exists in Dokan (Dokan, Inc.) dokan-lite plugin versions through 4.2.4 that allow
Privilege escalation in Dokan WordPress plugin versions 5.0.2 and earlier allows authenticated low-privileged customer a
Broken object-level authorization in the Dokan WordPress plugin (versions before 5.0.9) allows any authenticated vendor
Order ownership bypass in Dokan Multivendor for WordPress (versions before 5.0.9) allows any authenticated vendor to mod
The Dokan plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.0.8. Rate
PHP Object Injection in the Dokan Pro WordPress plugin (versions 5.0.2 and earlier) allows an authenticated user holding
Same technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-37835
GHSA-ghfc-6wf7-mhgw