WPCafe: A security weakness
WPCafe is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is n/a through 3.0.14.
- Component
- WPCafe
- Plugin slug
wp-cafe- Affected
- n/a through 3.0.14
- Safe version
3.0.15- Published
- Jun 26, 2026
- Weakness
- CWE-862 — Missing Authorization
This CVE was published Jun 26, 2026 and is one of 10 known issues for this plugin.
Update, patch or deactivate.
Update WPCafe to 3.0.15 or later, or disable and remove it until a fixed version is available.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
Subscriber Broken Access Control in WPCafe <= 3.0.14 versions.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N