Skip to main content
VulnerabilityPublished

CVE-2026-86816: WPCafe (WordPress plugin) · Information Exposure

Affects WPCafe (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 3.0.21 when convenient.

Data as of 21 Nov 2026, 17:35 UTC

CVSS 3.1 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 14% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 3.0.21
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.

What to do

Upgrade WPCafe (WordPress plugin) to 3.0.21.

Affected software

ProductAffectedFixed in
WPCafeAffected
  • <3.0.21
Fixed in
  • 3.0.21

AI-suggested

Upgrade WPCafe to version 3.0.21 or later, where access restrictions to the REST API endpoints have been implemented. No other mitigation is indicated by the vendor advisory. Patch status is confirmed by the version boundary provided.

Description

The WPCafe WordPress plugin before 3.0.21 does not restrict access to some of its REST API endpoints, allowing unauthenticated attackers to read WooCommerce product data, including per-product sales counts, exact stock levels, and private product meta, that WooCommerce itself keeps behind authentication.

References

Community reviews

Loading reviews…