dbcve.org
Information ExposureWeakness · CWE-200

CVE-2026-3504

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Dokan plugin's REST API endpoint /dokan/v1/stores/{id}/reviews exposes sensitive reviewer data including email addresses, usernames, and user IDs to unauthenticated users via the prepare_reviews_for_response method. This information disclosure affects all stores when store reviews are enabled with the Pro version active.

MitigationRemove sensitive PII fields (email, username, user_id) from the API response in the prepare_reviews_for_response method and implement proper authorization checks. Users should update to patched versions when available.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Dokan plugin is installed
    Check the WordPress plugins directory or admin panel for the Dokan plugin and note its version number
    Affected if Dokan plugin is installed with Pro version active and store reviews are enabled
  2. Confirm Pro version is active
    In WordPress admin, go to Dokan > Settings or check the plugin header to verify this is the Pro (commercial) version rather than the free version
    Affected if The Pro version is installed and active
  3. Check if store reviews are enabled
    Navigate to Dokan > Settings > General > Store Reviews or similar settings page and verify the store reviews feature is turned on
    Affected if Store reviews are enabled in the plugin settings
  4. Test unauthenticated API access
    Send a GET request to /wp-json/dokan/v1/stores/{store_id}/reviews without providing any authentication credentials
    Affected if The API endpoint responds successfully to unauthenticated requests
  5. Inspect API response for sensitive data
    Examine the JSON response from the API call for fields containing email addresses, usernames, or user_id values in the reviewer data objects
    Affected if The response includes email, username, or user_id fields for reviewers

A user is affected if they have Dokan Pro installed with store reviews enabled and the API endpoint returns sensitive reviewer information (email, username, user_id) to unauthenticated visitors.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Remove sensitive PII fields (email, username, user_id) from the API response in the prepare_reviews_for_response method and implement proper authorization checks. Users should update to patched versions when available.

Recommended fix Moderate confidence

Version 4.3.2 or later (latest stable release)

  1. 1. Navigate to the WordPress admin dashboard
  2. 2. Go to Plugins > Installed Plugins
  3. 3. Locate the Dokan plugin
  4. 4. If an update is available, click 'Update Now'
  5. 5. Alternatively, download the latest version from wordpress.org/plugins/dokan/ and upload via Plugins > Add New > Upload Plugin
  6. 6. Verify the update completed successfully
  7. 7. Confirm store reviews functionality still works as expected

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3504 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3504 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data