CVE-2024-31385

ReDi Restaurant Reservation <= 24.0128 - Cross-Site Request Forgery via redi_restaurant_admin_options_page()

2024-04-10 00:00
Joshua Chan

Strategic Overview

Status
Patched in 24.0303
Affected Version
<= 24.0128
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-31385
View all ReDi Restaurant Reservation – Instant Restaurant Booking & Table Reservation System vulnerabilities

At a glance

CVE-2024-31385 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the ReDi Restaurant Reservation WordPress plugin, affecting versions <= 24.0128. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 24.0303; sites on affected versions should update now. Disclosed April 2024, reported by Joshua Chan.

Vulnerability Overview

The ReDi Restaurant Reservation plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 24.0128. This is due to missing or incorrect nonce validation on the redi_restaurant_admin_options_page() function. This makes it possible for unauthenticated attackers to update plugin settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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 privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

ReDi Restaurant Reservation <= 24.0128 carries this weakness at redi_restaurant_admin_options_page(), and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For ReDi Restaurant Reservation the fix is 24.0303: builds <= 24.0128 are affected, anything from 24.0303 onward is not.

Remediation

Update to version 24.0303, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to ReDi Restaurant Reservation: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: ReDi Restaurant Reservation 24.0303 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

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