WP Hotel Booking <= 2.0.9.2 - Improper Authorization on Multiple REST API Routes

2024-02-03 00:00
Anonymous

Strategic Overview

Status
Patched in 2.0.9.3
Affected Plugin
WP Hotel Booking
Affected Version
<= 2.0.9.2
CVSS
6.5Medium
Weakness type
CWE-285 · Improper Authorization
CVE
CVE pending
View all WP Hotel Booking vulnerabilities

At a glance

This record tracks a medium-severity Improper Authorization vulnerability in the WP Hotel Booking WordPress plugin, affecting versions <= 2.0.9.2. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.9.3; sites on affected versions should update now. Disclosed February 2024.

Vulnerability Overview

The WP Hotel Booking plugin for WordPress is vulnerable to unauthorized access of data and modification of data due to an improper capability check on the 'pricing_plans', 'block_date', 'manager_bookings', and 'update_field_room' functions for the 'pricing-plans', 'block-date', 'manager-bookings', and 'update-field' REST routes, respectively, in versions up to, and including, 2.0.9.2. This makes it possible for unauthenticated attackers to expose sensitive information about bookings or modify them.

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-285: Improper Authorization

WP Hotel Booking <= 2.0.9.2 carries this weakness at pricing_plans, and reaching it takes a caller who can reach the endpoint. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.

A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For WP Hotel Booking the fix is 2.0.9.3: builds <= 2.0.9.2 are affected, anything from 2.0.9.3 onward is not.

Remediation

Update to version 2.0.9.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: WP Hotel Booking 2.0.9.3 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