CVE-2022-4340

BookingPress <= 1.0.30 - Unauthenticated Insecure Direct Object Reference

2022-12-07 00:00
Hussien Misbah

Strategic Overview

Status
Patched in 1.0.31
Affected Plugin
Appointment Booking Calendar Plugin and Scheduling Plugin – BookingPress
Affected Version
<= 1.0.30
CVSS
6.5Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2022-4340
View all Appointment Booking Calendar Plugin and Scheduling Plugin – BookingPress vulnerabilities

At a glance

CVE-2022-4340 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.30. 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 1.0.31; sites on affected versions should update now. Disclosed December 2022, reported by Hussien Misbah.

Vulnerability Overview

The BookingPress plugin for WordPress is vulnerable to insecure direct object reference in versions up to, and including, 1.0.30. This is due to insufficient validation on the 'appointment_id' user-controlled key. This makes it possible for unauthenticated attackers to retrieve booking information that includes booked services along with the name and time of booking.

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

Appointment Booking Calendar Plugin and Scheduling Plugin <= 1.0.30 carries this weakness at appointment_id, and reaching it takes no account at all. 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.31: builds <= 1.0.30 are affected, anything from 1.0.31 onward is not.

Remediation

Update to version 1.0.31, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Appointment Booking Calendar Plugin and Scheduling Plugin 1.0.31 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-4340https://www.wordfence.com/threat-intel/vulnerabilities/id/8019da67-fd2c-48f8-8983-6fb8fb30510bhttps://nvd.nist.gov/vuln/detail/CVE-2022-4340

Related records

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