CVE-2026-3504 MEDIUM

CVE-2026-3504: Dokan: AI Powered WooCommerce Multivendor Marketplace Solution <= 4.3.1 - Unauthenticated Information Disclosure in Store Reviews REST API Endpoint

Vendor Dokaninc
Product Dokan: AI Powered WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy
Weakness CWE-200 · Info exposure
Published May 2, 2026
Last update May 4, 2026

CVSS base score

5.3/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality Low
Integrity None

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

What the vulnerability does

01Description

The Dokan: AI Powered WooCommerce Multivendor Marketplace Solution plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 4.3.1 via the '/dokan/v1/stores/{id}/reviews' REST API endpoint. This is due to the 'prepare_reviews_for_response' method including reviewer email addresses, usernames, and user IDs in the API response. This makes it possible for unauthenticated attackers to extract email addresses, usernames, and user IDs of all customers who left reviews on any vendor's store. The Pro version of the plugin must be installed and activated, with store reviews enabled, in order to exploit the vulnerability.

Explanation of Vulnerability in Simple Terms

02Summary

Dokan versions up to 4.3.1 expose sensitive information that an unauthenticated attacker can access over the network without user interaction. The vulnerability stems from improper access controls on data that should be restricted. Site administrators should update to a version newer than 4.3.1 to mitigate exposure of confidential information.

What an attacker can do

03Attacker Capabilities

Read sensitive information from the marketplace without authentication.

Potential impact on your site

04Site Impact

Confidential marketplace data may be exposed to unauthorized parties.

Conditions required to exploit

05Prerequisites

Network access only; no authentication or user interaction required.

Key dates

06Disclosure timeline

May 2, 2026 CVE published
May 4, 2026 Record updated

Related vulnerabilities

08Related CVE