CVE-2025-4691

Free Booking Plugin for Hotels, Restaurants and Car Rentals – eaSYNC Booking <= 1.3.21 - Insecure Direct Object Reference to Sensitive Information Exposure

2025-05-30 21:32
cucumbersalad

Strategic Overview

Status
Patched in 1.3.22
Affected Version
<= 1.3.21
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2025-4691
View all eaSYNC Booking – Hotels, Restaurants & Car Rentals vulnerabilities

At a glance

CVE-2025-4691 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the eaSYNC Booking WordPress plugin, affecting versions <= 1.3.21. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.3.22; sites on affected versions should update now. Disclosed May 2025, reported by cucumbersalad.

Vulnerability Overview

The Free Booking Plugin for Hotels, Restaurants and Car Rentals – eaSYNC Booking plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.3.21 via the 'view_request_details' due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to view the details of any booking request. The vulnerability was partially patched in versions 1.3.18 and 1.3.21.

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, and no interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

eaSYNC Booking <= 1.3.21 carries this weakness at view_request_details, and reaching it takes a caller who can reach the endpoint. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For eaSYNC Booking the fix is 1.3.22: builds <= 1.3.21 are affected, anything from 1.3.22 onward is not.

Remediation

Update to version 1.3.22, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: eaSYNC Booking 1.3.22 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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