dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-12077

HIGH · 7.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 →
84/100
Remediation priority · High
Remotely reachable No privileges 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 via 'latitude' and 'longitude' parameters 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 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 versions up to 5.0.4 contains a time-based SQL injection vulnerability in the 'latitude' and 'longitude' parameters. Unauthenticated attackers can exploit insufficient input escaping combined with unprepared SQL queries to inject malicious SQL code and extract sensitive data from the database.

MitigationUpdate Dokan Pro plugin to a version beyond 5.0.4 when available, or apply vendor-provided security patches. Until patched, consider disabling the affected functionality or implementing a WAF rule to block malicious latitude/longitude parameter values.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Check Dokan Pro plugin version
    In the WordPress admin dashboard, navigate to Plugins > Installed Plugins and locate Dokan Pro. Note the version number displayed. Compare this version against the affected range: versions up to and including 5.0.4 are vulnerable.
    Affected if The installed version is 5.0.4 or lower
  2. Confirm latitude/longitude feature is accessible
    Determine if the site uses Dokan Pro location features such as store geolocation, delivery zones, or product location mapping. These features accept latitude and longitude parameters and are typically accessible without authentication.
    Affected if Location-based features that accept latitude/longitude parameters are enabled and publicly accessible
  3. Review plugin file for vulnerable code pattern
    Inspect the Dokan Pro plugin files, specifically looking for SQL query handling related to latitude and longitude parameters. The vulnerability exists where these parameters are used in unprepared SQL queries without proper escaping.
    Affected if The plugin code contains direct use of latitude/longitude parameters in SQL queries without prepared statements

The environment is affected if Dokan Pro version 5.0.4 or lower is installed and the latitude/longitude feature accepting user input is active.

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

Update Dokan Pro plugin to a version beyond 5.0.4 when available, or apply vendor-provided security patches. Until patched, consider disabling the affected functionality or implementing a WAF rule to block malicious latitude/longitude parameter values.

Recommended fix Moderate confidence

Dokan Pro 5.0.5 or later

  1. Identify the currently installed Dokan Pro plugin version in WordPress
  2. Log in to your WordPress admin dashboard
  3. Navigate to Plugins > Installed Plugins
  4. Locate Dokan Pro and note the current version
  5. Purchase and download Dokan Pro version 5.0.5 or later from dokan.co
  6. Deactivate the existing Dokan Pro plugin
  7. Delete the existing Dokan Pro plugin files
  8. Upload and install the new version (5.0.5 or later)
Caveat Review Dokan Pro release notes for version 5.0.5 to check for any feature changes or migration requirements before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation5.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,110
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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