CVE-2026-73395

Booking calendar, Appointment Booking System <= 3.2.36 - Unauthenticated Insecure Direct Object Reference

2026-08-18 00:00
Jakub Herman

Strategic Overview

Status
Unpatched
Affected Version
<= 3.2.36
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-73395
View all Booking calendar, Appointment Booking System vulnerabilities

At a glance

CVE-2026-73395 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Booking calendar, Appointment Booking System WordPress plugin, affecting versions <= 3.2.36. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed August 2026, reported by Jakub Herman.

Vulnerability Overview

The Booking calendar, Appointment Booking System plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.2.36. This is due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to perform an unauthorized action.

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

Reaching this weakness in Booking calendar, Appointment Booking System <= 3.2.36 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. No fixed build of this plugin is recorded for Booking calendar, Appointment Booking System yet, so installs running <= 3.2.36 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Login Security
  • Alerts

External References

Related records

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