CVE-2026-2230

Booking Calendar <= 10.14.14 - Insecure Direct Object Reference to Authenticated (Subscriber+) Arbitrary User Settings Modification

2026-02-17 00:00
Tarcísio Luchesi De Almeida Silva (Poystick)

Strategic Overview

Status
Patched in 10.14.15
Affected Plugin
Booking Calendar
Affected Version
<= 10.14.14
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-2230
View all Booking Calendar vulnerabilities

At a glance

CVE-2026-2230 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Booking Calendar WordPress plugin, affecting versions <= 10.14.14. 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 10.14.15; sites on affected versions should update now. Disclosed February 2026, reported by Tarcísio Luchesi De Almeida Silva (Poystick).

Vulnerability Overview

The Booking Calendar plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 10.14.14 via the handle_ajax_save function due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, and booking permissions granted by an Administrator, to modify other users' plugin settings, such as booking calendar display options, which can disrupt the booking calendar functionality for the targeted user.

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 Booking Calendar <= 10.14.14 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 Booking Calendar the fix is 10.14.15: builds <= 10.14.14 are affected, anything from 10.14.15 onward is not.

Remediation

Update to version 10.14.15, 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 Calendar 10.14.15 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-2230https://www.wordfence.com/threat-intel/vulnerabilities/id/60f7df44-22f9-4a9e-a20c-4b8628674079https://nvd.nist.gov/vuln/detail/CVE-2026-2230

Related records

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