dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-12079

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click 8 weeks old

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 time-based SQL Injection via the ’orderby’ parameter in all versions up to, and including, 5.0.4 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with Subscriber-level access and above, 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 sanitize and escape the 'orderby' parameter before using it in SQL queries, combined with insufficient use of prepared statements. This allows authenticated users with Subscriber-level access or higher to inject arbitrary SQL commands, specifically time-based blind SQL injection that can be used to extract sensitive data from the database.

MitigationUpdate Dokan Pro to the latest version which should contain patched code, or implement proper escaping of the orderby parameter using WordPress's $wpdb->prepare() method with strict allowlist validation for permitted sorting columns.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 Pro is installed
    Check the WordPress plugins directory (wp-content/plugins/) for the dokan-pro folder, or view the Plugins page in WordPress admin panel to confirm Dokan Pro is active.
    Affected if Dokan Pro plugin is not installed on the WordPress site.
  2. Check installed Dokan Pro version
    In WordPress admin, go to Plugins > Installed Plugins > Dokan Pro and read the version number from the plugin header, or inspect the main plugin file (e.g., includes/Dokan_Pro.php) for the 'Version' header comment.
    Affected if The installed version matches or falls within the vulnerable version range (confirm against vendor release notes for the patched version).
  3. Confirm presence of subscriber-level user accounts
    Navigate to Users > All Users in WordPress admin and check if any users exist with the Subscriber role, or use wp_users table to query for user roles.
    Affected if Any authenticated user with Subscriber-level access or higher exists on the site, allowing them to trigger the vulnerable parameter.
  4. Inspect orderby parameter handling in Dokan Pro code
    Review the Dokan Pro source code for endpoints that accept an 'orderby' parameter and construct SQL queries without using $wpdb->prepare() with proper placeholder substitution, specifically looking for direct concatenation of $_GET['orderby'] or similar input into ORDER BY clauses.
    Affected if Code contains direct insertion of the orderby parameter into SQL ORDER BY clauses without allowlist validation and proper prepared statement usage.

Your environment is affected if Dokan Pro is installed with a vulnerable version, and any authenticated user with Subscriber-level access or higher can access the site to trigger the unsanitized orderby parameter in SQL queries.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Dokan Pro to the latest version which should contain patched code, or implement proper escaping of the orderby parameter using WordPress's $wpdb->prepare() method with strict allowlist validation for permitted sorting columns.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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