dbcve.org
DokanWordPress extension

CVE-2023-34382

HIGH · 8.8 CVSS v3.1 Published 2023-12-19
Fix available
A fix is available. Upgrade to 3.7.20 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Deserialization of Untrusted Data 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.19.

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 · moderate confidence

Deserialization of Untrusted Data vulnerability in the Dokan WordPress/WooCommerce multivendor marketplace plugin allows attackers to potentially execute arbitrary code or manipulate data by supplying malicious serialized input.

MitigationUpdate Dokan plugin to version 3.7.20 or later which contains the patched version addressing the deserialization vulnerability.

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.20

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
High

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

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
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Dokan' in the list of installed plugins, or check your site's wp-content/plugins/ directory for a 'dokan' folder.
    Affected if Dokan plugin is not present on the WordPress site, the site is not affected by this vulnerability.
  2. Check installed Dokan version
    In WordPress admin, go to Plugins > Installed Plugins and click on the Dokan plugin to view its version number. Alternatively, inspect the file /wp-content/plugins/dokan/readme.txt or the main plugin PHP file and look for the 'Version:' header in the plugin metadata.
    Affected if The displayed version number is less than 3.7.20 (for example, 3.7.19, 3.7.0, 3.6.0, etc.).
  3. Confirm the vulnerability type applies
    This vulnerability is a PHP deserialization flaw that requires the Dokan plugin to be active and processing untrusted serialized data. The vulnerability exists in the plugin code itself, not in a specific configuration that can be disabled.
    Affected if The Dokan plugin is active and running a version below 3.7.20, the site is potentially vulnerable to deserialization attacks.

A WordPress site is affected if the Dokan plugin is installed and running any version lower than 3.7.20.

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.20 or later
Fixed in 3.7.20
Interim mitigation

Update Dokan plugin to version 3.7.20 or later which contains the patched version addressing the deserialization vulnerability.

Recommended fix High confidence

3.7.20

  1. Backup your WordPress site and database before performing any updates
  2. Update the Dokan plugin to version 3.7.20 or later through the WordPress admin dashboard (Plugins > Updates or directly from the Dokan plugin page)
  3. Verify the update was successful by checking the installed version number
  4. Test critical vendor marketplace functionality (product creation, orders, withdrawals) to ensure the update did not break existing features
Caveat Minor security patch update - minimal expected risk, but test vendor functionality after updating

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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