CVE-2026-15238

Hotel Booking Lite <= 6.2.2 - Insecure Direct Object Reference to Authenticated (Subscriber+) Customer Data Modification

2026-08-06 00:00
Haitam Lazaar

Strategic Overview

Status
Patched in 6.2.3
Affected Plugin
MotoPress Hotel Booking
Affected Version
<= 6.2.2
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-15238
View all MotoPress Hotel Booking vulnerabilities

At a glance

CVE-2026-15238 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the MotoPress Hotel Booking WordPress plugin, affecting versions <= 6.2.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 6.2.3; sites on affected versions should update now. Disclosed August 2026, reported by Haitam Lazaar.

Vulnerability Overview

The Hotel Booking Lite plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 6.2.2. This is due to missing ownership verification on the customer_id parameter, allowing the customer record to be fetched directly from POST data without confirming it belongs to the authenticated user. This makes it possible for authenticated attackers, with subscriber-level access and above, to modify another user's customer profile data by supplying an arbitrary customer_id in the update_customer form submission.

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

CWE-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in MotoPress Hotel Booking <= 6.2.2 takes an account at Subscriber level or above. 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 MotoPress Hotel Booking the fix is 6.2.3: builds <= 6.2.2 are affected, anything from 6.2.3 onward is not.

Remediation

Update to version 6.2.3, 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: MotoPress Hotel Booking 6.2.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-15238https://www.wordfence.com/threat-intel/vulnerabilities/id/5b823a9d-40b2-4308-b732-4a02a06e03e9https://nvd.nist.gov/vuln/detail/CVE-2026-15238

Related records

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