Quick answers
- Is CVE-2026-86812 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-86812 being exploited in the wild.
- How severe is CVE-2026-86812?
- Medium severity, with a CVSS score of 6.5, published 11 September 2026.
- Which products and versions are affected?
- WPCafe WPCafe 3.0.10 through 3.0.17.
- Is there a fix for CVE-2026-86812?
- A patch was published on 2026-09-11: Fixed in version 3.0.18 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-86812 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-86812?
- Check whether anything you run is named in the advisory. 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 stems from improper permission callbacks in the food-orders REST API endpoints (/wpcafe/v2/food-orders) that return a response object instead of WP_Error/false/null on authorization failure. WordPress interprets this as a grant, allowing unauthenticated access. Additionally, the mutation and deletion handlers lack per-order ownership validation, enabling attackers to modify or trash any order. The issue affects versions 3.0.10 through 3.0.17 and requires only network access to a vulnerable WordPress installation with WooCommerce enabled; no authentication or user interaction is needed.
Affected products
- WPCafe WPCafe 3.0.10 through 3.0.17
Timeline
- 2026-09-09: disclosed
- 2026-09-11: patched: Fixed in version 3.0.18