dbcve.org
DokanWordPress extension

CVE-2023-26525

HIGH · 8.1 CVSS v3.1 Published 2023-12-20
Fix available
A fix is available. Upgrade to 3.7.13 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable 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
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in weDevs Dokan – Best WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy.This issue affects Dokan – Best WooCommerce Multivendor Marketplace Solution – Build Your Own Amazon, eBay, Etsy: from n/a through 3.7.12.

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

SQL Injection vulnerability in the Dokan WooCommerce multivendor plugin allows attackers to inject malicious SQL commands via unsanitized user input in affected code paths. The vulnerability exists in versions up to and including 3.7.12.

MitigationUpdate to the latest patched version of Dokan that addresses this SQL injection vulnerability, or implement proper input validation and prepared statements/parameterized queries for all database interactions.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DokanWordPress extension
Affected:< 3.7.13

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Check installed Dokan plugin version
    Log in to WordPress admin, go to Plugins > Installed Plugins, locate Dokan, and read the version number from the plugin description. Alternatively, check the file /wp-content/plugins/dokan/readme.txt or the main plugin header in /wp-content/plugins/dokan/includes/functions.php
    Affected if version displayed is 3.7.12 or lower
  2. Confirm plugin is active
    In WordPress admin > Plugins, verify that the Dokan plugin shows as 'Active'
    Affected if plugin is active and version is vulnerable
  3. Identify SQL query code paths (optional deeper inspection)
    Review plugin files for direct SQL queries using $wpdb->prepare or raw queries. Check vendor/product-related endpoints where user input (like search parameters, vendor IDs, or product IDs) is passed to database queries without proper escaping
    Affected if custom code or theme modifications pass unsanitized user input to Dokan database functions and version is vulnerable
  4. Check for recent security updates
    Review the Dokan plugin changelog (in readme.txt or WordPress plugin repository) for version 3.7.13 release notes mentioning SQL injection fixes
    Affected if changelog shows no fix for this CVE and version remains below 3.7.13

The environment is affected if the Dokan plugin version installed is 3.7.12 or earlier and the plugin is active in the WordPress installation.

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
Upgrade available Upgrade to 3.7.13 or later
Fixed in 3.7.13
Interim mitigation

Update to the latest patched version of Dokan that addresses this SQL injection vulnerability, or implement proper input validation and prepared statements/parameterized queries for all database interactions.

Recommended fix High confidence

Dokan 3.7.13

  1. 1. Create a complete backup of the WordPress site and database before making any changes
  2. 2. Navigate to WordPress admin dashboard > Plugins
  3. 3. Locate the Dokan plugin and check for available updates
  4. 4. Update Dokan to version 3.7.13 or later
  5. 5. Verify the update was successful by checking the installed version number
  6. 6. Test critical vendor and order management functionality to ensure the update did not break existing features
  7. 7. If available, review Dokan changelog for any additional required configuration changes

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

Fix this in Dokan Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-26525 — 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-2023-26525 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