dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-11818

MEDIUM · 5.4 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WPCafe WordPress plugin up to 3.0.14 fails to verify user capabilities on REST API endpoints managing notification flow workflows. The endpoints only check for a wp_rest nonce, which is exposed in the frontend HTML of any logged-in page. This allows authenticated users with subscriber-level privileges (the lowest WordPress role) to perform administrative operations including create, read, update, delete, clone, and bulk-delete on notification workflows intended only for administrators.

MitigationUpdate the WPCafe plugin to version 3.0.15 or later which includes proper capability verification using current_user_can() checks before allowing workflow modifications. Until patched, monitor access logs for unauthorized notification workflow modifications.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm WPCafe plugin is installed
    Navigate to WordPress admin > Plugins and locate WPCafe, or check /wp-content/plugins/ directory for the wpcafe folder, or query the database wp_options table for option_name containing 'wpcafe'
    Affected if WPCafe plugin is present in the WordPress installation
  2. Identify installed WPCafe version
    In WordPress admin > Plugins, click on the WPCafe plugin to view version details, or read the main plugin file header in /wp-content/plugins/wpcafe/wp-cafe.php for 'Version:' tag
    Affected if Version is 3.0.14 or lower (any version up to and including 3.0.14)
  3. Verify notification workflow REST API endpoints exist
    Check if REST routes under /wp-json/wpcafe/v1/notifications or similar paths are registered by reviewing plugin source code in /wp-content/plugins/wpcafe/includes/ or using a REST API inspector to query /wp-json/
    Affected if Notification workflow API endpoints are present and active
  4. Confirm subscriber role has access to workflow endpoints
    Using a test subscriber account, send a REST API request (GET/POST/PUT/DELETE) to the wpcafe notification endpoints with only a valid wp_rest nonce (obtainable from any logged-in page source), or inspect capability checks in the plugin REST controller code
    Affected if Subscriber-level user can successfully modify notification workflows without administrator capabilities

You are affected if WPCafe plugin version is 3.0.14 or lower AND the notification workflow REST API endpoints are accessible to subscriber-level users without proper capability verification.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WPCafe plugin to version 3.0.15 or later which includes proper capability verification using current_user_can() checks before allowing workflow modifications. Until patched, monitor access logs for unauthorized notification workflow modifications.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-11818 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-11818 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data