Quick answers
- Is CVE-2026-12224 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-12224 being exploited in the wild.
- How severe is CVE-2026-12224?
- High severity, with a CVSS score of 8.8, published 1 July 2026.
- Which products and versions are affected?
- weDevs Dokan Pro up to, and including, 5.0.4.
- Is there a fix for CVE-2026-12224?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-12224 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-12224?
- Check whether you run weDevs Dokan Pro at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The Dokan Pro plugin for WordPress is vulnerable to privilege escalation due to an insecure implementation of the `update_capabilities()` REST handler. The function accepts arbitrary capability strings from a request body and passes them directly to the `WP_User::add_cap()` function without validating them against an allowlist. While the endpoint checks if the requester has 'dokandar' (vendor) capabilities, it does not prevent them from assigning high-level permissions like 'administrator' to vendor staff accounts. This vulnerability requires the Vendor Staff module to be enabled and can be exploited by any authenticated user with Vendor-level access or higher to achieve full site takeover. All versions up to and including 5.0.4 are affected.
Affected products
- weDevs Dokan Pro up to, and including, 5.0.4
Timeline
- 2026-07-01: advisory: NVD publication date
- 2026-07-01: disclosed: Wordfence vulnerability report published