CVE-2024-31296

BookingPress <= 1.0.81 - Authenticated (Customer+) Insecure Direct Object Reference

2024-04-05 00:00
Steven Julian

Strategic Overview

Status
Patched in 1.0.82
Affected Plugin
Appointment Booking Calendar Plugin and Scheduling Plugin – BookingPress
Affected Version
<= 1.0.81
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2024-31296
View all Appointment Booking Calendar Plugin and Scheduling Plugin – BookingPress vulnerabilities

At a glance

CVE-2024-31296 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Appointment Booking Calendar Plugin and Scheduling Plugin WordPress plugin, affecting versions <= 1.0.81. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Customer level or above. The issue is fixed in version 1.0.82; sites on affected versions should update now. Disclosed April 2024, reported by Steven Julian.

Vulnerability Overview

The BookingPress – Appointment Booking Calendar Plugin and Online Scheduling Plugin plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.0.81 due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with customer-level access and above, to access or perform an action on an object they should not have access to.

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 Appointment Booking Calendar Plugin and Scheduling Plugin <= 1.0.81 takes an account at Customer 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 Appointment Booking Calendar Plugin and Scheduling Plugin the fix is 1.0.82: builds <= 1.0.81 are affected, anything from 1.0.82 onward is not.

Remediation

Update to version 1.0.82, 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: Appointment Booking Calendar Plugin and Scheduling Plugin 1.0.82 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-31296https://www.wordfence.com/threat-intel/vulnerabilities/id/a86fc949-6caf-48b7-beda-ca0c653c9b29https://nvd.nist.gov/vuln/detail/CVE-2024-31296

Related records

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