← WordPress Vulnerabilities
WordPress security by component

Dokan Pro

Dokan Pro is a WordPress component with 11 published CVE records in this archive. The latest tracked vulnerability was published Jul 23, 2026; the highest CVE/CNA score is 9.8.

Plugin slug: dokan-pro

CVE-2026-65495: Dokan Pro: A security weakness

Dokan Pro is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 5.0.3.

PublishedJul 23, 2026
Known safe version> 5.0.3
Safe version
Jul 23, 2026 CVE-2026-65495
Dokan Pro: A security weakness
Dokan Pro is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 5.0.3.
> 5.0.3
CVE7.5
NVDPending
Jul 23, 2026 CVE-2026-65494
Dokan Pro: SQL injection
Dokan Pro is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data. The published affected range is n/a through 5.0.2.
> 5.0.2
CVE7.1
NVDPending
Jul 23, 2026 CVE-2026-65493
Dokan Pro: Code execution
Dokan Pro is affected by code execution. Exposure depends on how the affected operation is made reachable by the site. Successful exploitation can run attacker-controlled code in the WordPress hosting account. The published affected range is n/a through 5.0.2.
> 5.0.2
CVE7.5
NVDPending
Jul 23, 2026 CVE-2026-65492
Dokan Pro: Cross-site scripting
Dokan Pro is affected by cross-site scripting. The vulnerable path is reachable without authentication. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is n/a through 5.0.0.
> 5.0.0
CVE7.1
NVDPending
Jul 01, 2026 CVE-2026-12224
Dokan Pro: Privilege escalation or authentication bypass
Dokan Pro is affected by privilege escalation or authentication bypass. Exploitation requires an authenticated WordPress account. A successful request can grant permissions or access that the caller should not possess. The published affected range is <= 5.0.4.
> 5.0.4
CVE8.8
NVDPending
Jun 26, 2026 CVE-2026-56033
Dokan Pro: Privilege escalation or authentication bypass
Dokan Pro is affected by privilege escalation or authentication bypass. The vulnerable path is reachable without authentication. A successful request can grant permissions or access that the caller should not possess. The published affected range is n/a through 5.0.4.
5.0.5
CVE9.8
NVDPending
Jun 25, 2026 CVE-2026-12079
Dokan Pro: SQL injection
Dokan Pro is affected by SQL injection. Exploitation requires at least subscriber-level access. A successful request can alter database queries and expose or modify WordPress data. The published affected range is <= 5.0.4.
> 5.0.4
CVE6.5
NVDPending
Jun 25, 2026 CVE-2026-12077
Dokan Pro: SQL injection
Dokan Pro is affected by SQL injection. The vulnerable path is reachable without authentication. A successful request can alter database queries and expose or modify WordPress data. The published affected range is <= 5.0.4.
> 5.0.4
CVE7.5
NVDPending
Jan 05, 2026 CVE-2025-39497
Dokan Pro: Cross-site scripting
Dokan Pro is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
See mitigation notes
CVE6.5
NVDPending
Dec 16, 2025 CVE-2025-12809
Dokan Pro: A security weakness
Dokan Pro is affected by a security weakness. The vulnerable path is reachable without authentication. The resulting impact depends on how the affected component exposes the vulnerable operation.
See mitigation notes
CVE5.3
NVDPending
Aug 26, 2025 CVE-2025-5931
Dokan Pro: Privilege escalation or authentication bypass
Dokan Pro is affected by privilege escalation or authentication bypass. Exploitation requires an authenticated WordPress account. A successful request can grant permissions or access that the caller should not possess.
See mitigation notes
CVE8.8
NVDPending