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

New CVE Detected

CVE-2026-56033 – Unauthenticated Privilege Escalation – Dokan Pro WordPress Plugin <= 5.0.4

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

Summary

CVE-2026-56033 is a critical unauthenticated privilege escalation vulnerability in the Dokan Pro WordPress plugin, affecting all versions up to and including 5.0.4. With a CVSS v3.1 score of 9.8 (Critical), the flaw allows any remote, unauthenticated attacker to escalate their privileges on an affected WordPress site with no user interaction required. Sites running Dokan Pro as a WooCommerce multivendor marketplace are directly at risk of complete administrative compromise.

Technical details

  • Root cause: The vulnerability stems from incorrect privilege assignment (CWE-266) within the Dokan Pro plugin. Insufficient authentication and authorization controls allow unauthenticated requests to trigger privileged operations, enabling an attacker to obtain elevated — up to administrator-level — access without any credentials.
  • Trigger conditions: The flaw is exploitable by any unauthenticated network attacker. No prior account, authentication token, or user interaction is needed to trigger it.
  • Attack vector: Remotely accessible over the network (AV:N). Attack complexity is low (AC:L), meaning no special conditions or target configuration is required beyond the vulnerable plugin being active.
  • Impact: Successful exploitation grants full confidentiality, integrity, and availability impact (C:H/I:H/A:H). An attacker can gain administrative control of the WordPress installation, enabling arbitrary content modification, user account takeover, malware injection, data exfiltration, and complete site compromise.
  • Automatable: CISA has assessed exploitation of this vulnerability as automatable, meaning it can be scripted and deployed at scale against internet-facing sites.

Affected software

  • Dokan Pro (WordPress plugin by Dokan Multivendor Plugin) — all versions ≤ 5.0.4

Severity

  • CVSS v3.1 Base Score: 9.8 (Critical)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate — patch now: Update the Dokan Pro plugin to version 5.0.5 or later, which contains the vendor-provided fix. Administrators should log in to their WordPress dashboard and apply the update immediately.
  • Audit access logs: Review recent WordPress administrator account activity for any unauthorized logins, new admin accounts, or unexpected privilege changes, particularly from the period prior to patching.
  • Network mitigation (if patching is not immediately possible): Restrict external access to WordPress admin endpoints (/wp-admin/, REST API routes under /dokan/v1/) via WAF rules or IP allowlisting until the patch can be applied.
  • Review installed plugin versions: Confirm the exact version of Dokan Pro in use via the WordPress dashboard (Plugins → Installed Plugins) and prioritize any internet-exposed instances.

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