CVE-2024-5431: WPCafe – Online Food Ordering, Restaurant Menu, Delivery, and Reservations for WooCommerce <= 2.2.25 - Authenticated (Contributor+) File inclusion via Shortcode

Published Jun 25, 2024
·
Updated

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 reservationextrafield 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

Affected Software

2 affected components
WPCafe Online Food Ordering, Restaurant Menu, Delivery, and Reservations for WooCommerce<=2.2.25
Themewinter Wpcafe Wordpress<2.2.26

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade WPCafe – Online Food Ordering, Restaurant Menu, Delivery, and Reservations for WooCommerce to a version that resolves this vulnerability.

    Fixed in 2.2.25

Event History

Jun 25, 2024
CVE Published
via MITRE·05:41 AM
Data Sourced
via MITRE·05:41 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·06:15 AM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2024-5431?

CVE-2024-5431 has been classified with a high severity due to its potential for Local File Inclusion attacks.

2

How do I fix CVE-2024-5431?

To fix CVE-2024-5431, update the WPCafe plugin to a version newer than 2.2.25.

3

What are the potential consequences of CVE-2024-5431?

Exploitation of CVE-2024-5431 can lead to unauthorized file access on the server hosting the WordPress site.

4

Which versions of WPCafe are affected by CVE-2024-5431?

All versions of the WPCafe plugin up to and including 2.2.25 are affected by CVE-2024-5431.

5

Is there a workaround for CVE-2024-5431?

As of now, the best approach for CVE-2024-5431 is to update to a patched version, as no official workaround has been provided.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203