Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-12077 – Unauthenticated SQL Injection – Dokan Pro WordPress Plugin ≤ 5.0.4

Be the first to know when new zero-days emerge:

Summary

CVE-2026-12077 is a high-severity, time-based SQL injection vulnerability in the Dokan Pro WordPress plugin (by weDevs), affecting all versions up to and including 5.0.4. The flaw is exploitable by unauthenticated, network-based attackers with no user interaction required, enabling extraction of sensitive data directly from the WordPress database. With Dokan Pro powering over 40,000 live multi-vendor marketplaces worldwide, the potential exposure is significant.

Technical details

  • Root cause: Insufficient escaping of user-supplied input combined with a lack of proper SQL query preparation in the processing of the latitude and longitude parameters.

  • Trigger conditions: No authentication is required. An attacker can send a crafted HTTP request containing malicious values in the latitude or longitude parameters to trigger the injection.

  • Attack vector: Unauthenticated and network-accessible — CVSS attributes AV:N (Network), AC:L (Low Complexity), PR:N (No Privileges), UI:N (No User Interaction). The attack requires no foothold within the target environment.

  • Impact: By appending additional SQL statements to existing queries, an attacker can extract sensitive information from the WordPress database, including user credentials, vendor records, order data, and personally identifiable information (PII) stored on the platform.

Affected software

  • Dokan Pro (by weDevs) — all versions up to and including 5.0.4

Severity

  • CVSS v3.1 Base Score: 7.5 (HIGH)

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

Mitigation and recommended actions

  • Immediate: Update Dokan Pro to version 5.0.5 or later, which resolves this vulnerability.

  • If immediate patching is not possible: Apply web application firewall (WAF) rules to block SQL metacharacters in the latitude and longitude request parameters, and restrict public network access to affected endpoints where feasible until the patch can be applied.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge