Quick answers
- Is CVE-2026-66699 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-66699 being exploited in the wild.
- How severe is CVE-2026-66699?
- Medium severity, with a CVSS score of 5.3, published 6 August 2026.
- Which products and versions are affected?
- weDevs Dokan <=5.0.10.
- Is there a fix for CVE-2026-66699?
- A patch was published on 2026-07-29: patched in version 5.0.11 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-66699 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-66699?
- Check whether you run weDevs Dokan 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 vulnerability is a broken access control issue in Dokan versions up to 5.0.10 affecting custom role handling. Users with custom roles can bypass access restrictions and perform actions outside their intended permissions, potentially viewing sensitive data or performing unauthorized administrative operations. The attack requires authentication as a user with a custom role. The vulnerability is present in all versions through 5.0.10 and has been patched in version 5.0.11 or later.
Affected products
- Wedevs Dokan <=5.0.10
Timeline
- 2026-07-29: disclosed
- 2026-07-29: patched: patched in version 5.0.11