CVE-2026-11818

WPCafe <= 3.0.14 - Missing Authorization to Authenticated (Subscriber+) Arbitrary Modification via REST API

2026-07-09 14:47
Sushi Com Abacate

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
5.4Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2026-11818
View all WPCafe – Restaurant Menu, Online Food Ordering & Table Booking System vulnerabilities

At a glance

CVE-2026-11818 is a medium-severity Missing Authorization vulnerability in the WPCafe WordPress plugin, affecting versions <= 3.0.14. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 3.0.15; sites on affected versions should update now. Disclosed July 2026, reported by Sushi Com Abacate.

Vulnerability Overview

The WPCafe – Restaurant Menu, Online Food Ordering & Table Booking System plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 3.0.14. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to list, create, update, delete, clone, and bulk-delete notification flow workflows that are intended to be managed only by administrators. The only protection on these endpoints is a wp_rest nonce check, which is obtainable by any logged-in user from the frontend page source.

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 an account at Subscriber level or above. 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-11818https://www.wordfence.com/threat-intel/vulnerabilities/id/9cf2d3bd-359c-4334-ad28-b6b9722edd1chttps://nvd.nist.gov/vuln/detail/CVE-2026-11818

Related records

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