CVE-2026-57622

WPCafe – Restaurant Menu, Online Food Ordering & Table Booking System <= 3.0.14 - Missing Authorization

2026-06-25 00:00
L4m

Strategic Overview

Status
Patched in 3.0.15
Affected Plugin
WPCafe – Restaurant Menu, Online Food Ordering & Table Booking System
Affected Version
<= 3.0.14
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-57622
View all WPCafe – Restaurant Menu, Online Food Ordering & Table Booking System vulnerabilities

At a glance

CVE-2026-57622 is a medium-severity Missing Authorization vulnerability in the WPCafe WordPress plugin, affecting versions <= 3.0.14. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 3.0.15; sites on affected versions should update now. Disclosed June 2026, reported by L4m.

Vulnerability Overview

The WPCafe – Restaurant Menu, Online Food Ordering & Table Booking System plugin for WordPress is vulnerable to unauthorized access due to a missing capability check on a function in versions up to, and including, 3.0.14. This makes it possible for authenticated attackers, with subscriber-level access and above, to perform an unauthorized action.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in WPCafe <= 3.0.14 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WPCafe the fix is 3.0.15: builds <= 3.0.14 are affected, anything from 3.0.15 onward is not.

Remediation

Update to version 3.0.15, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WPCafe 3.0.15 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-57622https://www.wordfence.com/threat-intel/vulnerabilities/id/d7b40225-d994-43d2-8e8f-2dae271be9behttps://nvd.nist.gov/vuln/detail/CVE-2026-57622

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C