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.
CVE-2026-11818
MEDIUMPre-NVD 5.45.4—Trending — 4 sources updated this week
EchelonGraph scoreHIGH confidence
Score 5.4 from GitHub Security Advisory published 2026-07-10. a secondary CVSS source baseline 5.4; sources differ by 0.0.
Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
5.4
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.4Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.4
- EG Score
- 5.4(high)
- EPSS
- 16.4%
- KEV
- Not listed
Published
July 10, 2026
Last Modified
July 10, 2026
References (10)
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-cafe/tags/3.0.13/vendor/themewinter/email-notification-sdk/src/Flow/FlowAPI.php#L102
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-cafe/tags/3.0.13/vendor/themewinter/email-notification-sdk/src/Flow/FlowAPI.php#L110
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-cafe/tags/3.0.13/vendor/themewinter/email-notification-sdk/src/Flow/FlowAPI.php#L121
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-cafe/tags/3.0.13/vendor/themewinter/email-notification-sdk/src/Flow/FlowAPI.php#L66
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-cafe/tags/3.0.13/vendor/themewinter/email-notification-sdk/src/Flow/FlowAPI.php#L74
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-cafe/tags/3.0.13/vendor/themewinter/email-notification-sdk/src/Flow/FlowAPI.php#L82
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-cafe/tags/3.0.15/core/email-automation/Service/email-notification.php#L119
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-cafe/tags/3.0.15/core/email-automation/Service/email-notification.php#L78
- security@wordfencehttps://plugins.trac.wordpress.org/browser/wp-cafe/tags/3.0.15/core/email-automation/Service/email-notification.php#L88
- security@wordfencehttps://www.wordfence.com/threat-intel/vulnerabilities/id/9cf2d3bd-359c-4334-ad28-b6b9722edd1c?source=cve
Vendor Advisories for CVE-2026-11818(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 20× in last 7d / 20× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-16 00:52 UTCEG score recompute
- 2026-07-16 00:51 UTCGHSA enrichment
- 2026-07-15 16:57 UTCEPSS rescore
- 2026-07-15 02:00 UTCEPSS rescore
- 2026-07-15 01:20 UTCEG score recompute
- 2026-07-15 01:20 UTCGHSA enrichment
- 2026-07-14 01:50 UTCEG score recompute
- 2026-07-14 01:50 UTCGHSA enrichment
- 2026-07-13 22:30 UTCEPSS rescore
- 2026-07-13 06:12 UTCEPSS rescore
- 2026-07-13 02:20 UTCEG score recompute
- 2026-07-13 02:20 UTCGHSA enrichment
- 2026-07-12 05:46 UTCEPSS rescore
- 2026-07-12 02:50 UTCEG score recompute
- 2026-07-12 02:50 UTCGHSA enrichment
- 2026-07-11 08:27 UTCEPSS rescore
- 2026-07-11 03:20 UTCEG score recompute
- 2026-07-11 03:20 UTCGHSA enrichment
- 2026-07-10 03:50 UTCEG score recompute
- 2026-07-10 03:48 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
Frequently asked(5)
What is CVE-2026-11818?
CVE-2026-11818 is a medium vulnerability published on July 10, 2026. 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…
When was CVE-2026-11818 disclosed?
CVE-2026-11818 was first published in the National Vulnerability Database on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11818 actively exploited?
CVE-2026-11818 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-11818?
CVE-2026-11818 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-11818?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11818, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-11818
Is Your Infrastructure Affected by CVE-2026-11818?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.