dbcve.org
WpcafeWordPress extension · Themewinter

CVE-2024-5431

HIGH · 8.8 CVSS v3.1 Published 2024-06-25
Fix available
A fix is available. Upgrade to 2.2.26 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 – Online Food Ordering, Restaurant Menu, Delivery, and Reservations for WooCommerce plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 2.2.25 via the reservation_extra_field shortcode parameter. This makes it possible for authenticated attackers, with Contributor-level access and above, to include remote files on the server, potentially resulting in code execution

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 plugin for WordPress contains a Local File Inclusion vulnerability in versions up to 2.2.25. Attackers with Contributor-level access or higher can exploit the reservation_extra_field shortcode parameter to include arbitrary remote files on the server, potentially achieving remote code execution.

MitigationUpdate the WPCafe plugin to version 2.2.26 or later. If updates are unavailable, disable the reservation_extra_field shortcode and restrict contributor-level user capabilities until a patch is available.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WpcafeWordPress extension
Affected:< 2.2.26

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
High
Integrity
High
Availability
High

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

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
    Check WordPress plugin directory or access wp-admin/plugins.php and look for 'WPCafe' or 'Wpcafe' plugin
    Affected if Plugin named WPCafe or Wpcafe is found in the WordPress installation
  2. Identify installed WPCafe version
    View the plugin details in WordPress admin under Plugins > Installed Plugins, or inspect the main plugin file header for the version number
    Affected if Version is below 2.2.26 (e.g., 2.2.25 or earlier)
  3. Detect usage of reservation_extra_field shortcode
    Search WordPress database or posts/pages for the shortcode '[reservation_extra_field' or check if it is present in any page content
    Affected if The reservation_extra_field shortcode is being used in any post, page, or widget
  4. Check for Contributor-level or higher user accounts
    Review WordPress user roles in the admin panel under Users, or query the wp_usermeta table for users with 'contributor' capability or higher
    Affected if At least one user account with Contributor role or above exists in WordPress

The environment is affected if WPCafe plugin version below 2.2.26 is installed, the reservation_extra_field shortcode is in use, and users with Contributor-level or higher access exist.

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.

dbcve · scoped
Upgrade available Upgrade to 2.2.26 or later
Fixed in 2.2.26
Interim mitigation

Update the WPCafe plugin to version 2.2.26 or later. If updates are unavailable, disable the reservation_extra_field shortcode and restrict contributor-level user capabilities until a patch is available.

Recommended fix High confidence

WPCafe version 2.2.26

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find WPCafe – Online Food Ordering, Restaurant Menu, Delivery, and Reservations for WooCommerce
  4. Click 'Update now' if an update is available, or manually update to version 2.2.26 or later
  5. Verify the update was successful by checking the plugin version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wpcafe Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-5431 — 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-2024-5431 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