Quick answers
- Is CVE-2026-86816 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86816 being exploited in the wild.
- How severe is CVE-2026-86816?
- Informational severity, published 7 October 2026.
- Which products and versions are affected?
- WPCafe before 3.0.21.
- Is there a fix for CVE-2026-86816?
- Yes: fixed in 3.0.21. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-86816 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-86816?
- Check whether you run WPCafe 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.
How to fix
- Fixed in: 3.0.21
Technical details
The vulnerability is an authentication bypass in WPCafe's REST API endpoints that fails to validate user permissions before returning WooCommerce product data. Unauthenticated attackers can make network requests to these endpoints without credentials to retrieve sales counts, exact stock levels, and private product metadata. The vulnerability affects versions before 3.0.21.
Affected products
- WPCafe WPCafe before 3.0.21
Timeline
- 2026-10-05: disclosed
- 2026-10-07: advisory