CVE-2023-37389

Booking Package <= 1.5.98 - Authorization Bypass to Arbitrary Password Reset

2023-07-05 00:00
Rafie Muhammad

Strategic Overview

Status
Patched in 1.5.99
Affected Plugin
Booking Package
Affected Version
< 1.5.99
CVSS
9.8Critical
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2023-37389
View all Booking Package vulnerabilities

At a glance

CVE-2023-37389 is a critical-severity Authorization Bypass Through User-Controlled Key vulnerability in the Booking Package WordPress plugin, affecting versions < 1.5.99. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.5.99; sites on affected versions should update now. Disclosed July 2023, reported by Rafie Muhammad.

Vulnerability Overview

The Booking Package plugin for WordPress is vulnerable to Authorization Bypass in versions up to, and including 1.5.98 due to missing validation in the 'updateUser' function. This allows unauthenticated attackers to reset the email and password of any user on the site if they know the username. Note that only sites that have an active premium subscription are vulnerable.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-639: Authorization Bypass Through User-Controlled Key

Booking Package < 1.5.99 carries this weakness at updateUser, 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 Booking Package the fix is 1.5.99: builds < 1.5.99 are affected, anything from 1.5.99 onward is not.

Remediation

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

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-37389https://www.wordfence.com/threat-intel/vulnerabilities/id/65166432-a877-4070-94c1-cdaf7e5d7586https://nvd.nist.gov/vuln/detail/CVE-2023-37389

Related records

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