dbcve.org
DokanWordPress extension

CVE-2024-3922

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-13
Fix available
A fix is available. Upgrade to 3.11.0 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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 Pro plugin for WordPress is vulnerable to SQL Injection via the 'code' parameter in all versions up to, and including, 3.10.3 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

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 Pro WordPress plugin fails to properly escape the 'code' parameter and lacks prepared statements in its SQL queries, allowing unauthenticated attackers to inject arbitrary SQL commands. This can lead to complete database compromise including extraction of sensitive user data, passwords, and administrative credentials.

MitigationUpdate Dokan Pro to version 3.10.4 or later which contains the security patch. Until patched, consider disabling the plugin or implementing WAF rules to block SQL injection attempts on the affected parameter.

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

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Confirm Dokan plugin installation and location
    Check for the Dokan plugin directory in your WordPress installation at wp-content/plugins/dokan/ and list the files to verify the plugin is present.
    Affected if The Dokan plugin directory exists in the WordPress plugins folder.
  2. Determine the installed Dokan version
    Open the main Dokan plugin file (such as class-we-dokan.php or dokan.php in the plugin root) and locate the 'Version' header in the plugin comments, or check the readme.txt file for the 'Stable tag' or version number.
    Affected if The version number found is less than 3.11.0.
  3. Identify the vulnerable code parameter endpoint
    Search the Dokan plugin source code for handlers that process the 'code' parameter, typically in frontend/class-frontend.php or similar frontend processing files, and verify if this parameter is used in SQL queries without prepare() statements.
    Affected if Code exists that takes the 'code' parameter directly into an SQL query without using $wpdb->prepare() or similar prepared statement functions.
  4. Check if the vulnerable endpoint is publicly accessible
    Identify URLs/route handlers in Dokan that accept the 'code' parameter (commonly used for coupon codes, withdrawal codes, or similar redemption features) and determine if these are accessible to unauthenticated users by checking the route registration and access controls.
    Affected if The endpoint accepting the 'code' parameter does not require authentication and is reachable without a logged-in session.

Your environment is affected if Dokan Pro plugin is installed with a version below 3.11.0 and the 'code' parameter endpoint is publicly accessible without authentication.

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.11.0 or later
Fixed in 3.11.0
Interim mitigation

Update Dokan Pro to version 3.10.4 or later which contains the security patch. Until patched, consider disabling the plugin or implementing WAF rules to block SQL injection attempts on the affected parameter.

Recommended fix High confidence

Dokan Pro 3.11.0

  1. Create a full backup of your WordPress database and files before making any changes
  2. Update the Dokan Pro plugin to version 3.11.0 or later through the WordPress admin dashboard (Plugins > All Plugins > Dokan Pro > Update Now)
  3. Alternatively, upload Dokan Pro version 3.11.0 or newer manually via Plugins > Add New > Upload Plugin
  4. After updating, verify the plugin version shows 3.11.0 or higher in the installed plugins list
  5. Test critical vendor functionality (vendor dashboard, order processing, product management) to ensure the update did not break expected functionality
  6. Review the site for any unexpected behavior or errors in error logs

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

Fix this in Dokan Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
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,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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