Free tool
Is my WordPress plugin safe?
Type a plugin or theme and the version you run, and we’ll show every known vulnerability that affects it, from the 390,080 records in our vulnerability database. The version is listed under Plugins in your WordPress dashboard.
Plugin · dokan-pro
dokan-pro
12 known vulnerabilities on record. Add your version above to see which ones affect you.
Jul 23, 2026Unauthenticated Broken Access Control in Dokan Pro <= 5.0.3 versions.CVE-2026-65495 · affects up to 5.0.3 · reported by PatchstackHigh 7.5
Unauthenticated Broken Access Control in Dokan Pro <= 5.0.3 versions.
Jul 23, 2026Subscriber SQL Injection in Dokan Pro <= 5.0.2 versions.CVE-2026-65494 · affects up to 5.0.2 · reported by PatchstackHigh 7.1
Subscriber SQL Injection in Dokan Pro <= 5.0.2 versions.
Jul 23, 2026Subscriber PHP Object Injection in Dokan Pro <= 5.0.2 versions.CVE-2026-65493 · affects up to 5.0.2 · reported by PatchstackHigh 7.5
Subscriber PHP Object Injection in Dokan Pro <= 5.0.2 versions.
Jul 23, 2026Dokan Pro: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVE-2026-65492 · fixed in 5.0.7 · reported by PatchstackHigh 7.1
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in weDevs Dokan Pro allows Reflected XSS. This issue affects Dokan Pro: from n/a before 5.0.7.
Jul 1, 2026Dokan Pro: Privilege escalationCVE-2026-12224 · affects up to 5.0.4 · reported by WordfenceHigh 8.8
The Dokan Pro plugin for WordPress is vulnerable to privilege escalation via update_capabilities REST Endpoint in all versions up to, and including, 5.0.4. This is due to the `update_capabilities()` REST handler accepting arbitrary capability strings from the request body and passing them directly to WP_User::add_cap() with no allowlist validation, only verifying that the caller holds the dokandar capability. This makes it possible for authenticated attackers with a self-provisioned Vendor-level access and above, on sites with the Vendor Staff module enabled, to grant arbitrary WordPress capabilities, including administrator, to any vendor_staff account, leading to a full site takeover.
Jun 26, 2026Unauthenticated Privilege Escalation in Dokan Pro <= 5.0.4 versions.CVE-2026-56033 · reported by PatchstackCritical 9.8
Unauthenticated Privilege Escalation in Dokan Pro <= 5.0.4 versions.
Jun 25, 2026Dokan Pro: Time-based SQL InjectionCVE-2026-12079 · affects up to 5.0.4 · reported by WordfenceMedium 6.5
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.
Jun 25, 2026Dokan Pro: Time-based SQL InjectionCVE-2026-12077 · affects up to 5.0.4 · reported by WordfenceHigh 7.5
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.
Jan 5, 2026Dokan Pro: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')CVE-2025-39497 · affects up to 3.14.5 · reported by PatchstackMedium 6.5
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Dokan Dokan Pro allows Stored XSS.This issue affects Dokan Pro: from n/a through 3.14.5.
Dec 16, 2025Dokan Pro: Unauthorized access of dataCVE-2025-12809 · affects up to 4.1.3 · reported by WordfenceMedium 5.3
The Dokan Pro plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the `/dokan/v1/wholesale/register` REST API endpoint in all versions up to, and including, 4.1.3. This makes it possible for unauthenticated attackers to enumerate users and retrieve their email addresses via the REST API by providing a user ID, along with other information such as usernames, display names, user roles, and registration dates.
Aug 26, 2025Dokan Pro: Privilege escalationCVE-2025-5931 · affects up to 4.0.5 · reported by WordfenceHigh 8.8
The Dokan Pro plugin for WordPress is vulnerable to privilege escalation via account takeover in all versions up to, and including, 4.0.5. This is due to the plugin not properly validating a user's identity prior to updating their password during a staff password reset. This makes it possible for authenticated attackers, with vendor-level access and above, to elevate their privilege to the level of a staff member and then change arbitrary user passwords, including those of administrators in order to gain access to their accounts. By default, the plugin allows customers to become vendors.
Jun 12, 2024Dokan Pro: SQL InjectionCVE-2024-3922 · affects up to 3.10.3 · reported by WordfenceCritical 10
The Dokan Pro plugin for WordPress is vulnerable to SQL Injection via the 'code' parameter in all versions up to, and including, 3.10.3 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.
Versions are matched against the affected ranges published with each record. A plugin can ship a fix under its own numbering, so if something looks off, check the linked record. Want the whole site checked at once? Run the free website check.
Tell us what you're building.
A website, your marketing, a security check, an app, or the thing you've been running out of a spreadsheet for three years. A few lines is plenty.
Not ready to talk yet? Run the free website check and see what Google sees.