CVE-2026-6810

Booking Calendar Contact Form <= 1.2.63 - Authenticated (Subscriber+) Insecure Direct Object Reference to Calendar Takeover

2026-04-23 16:30
Md. Moniruzzaman Prodhan (NomanProdhan)

Strategic Overview

Status
Patched in 1.2.64
Affected Plugin
Booking Calendar Contact Form
Affected Version
<= 1.2.63
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-6810
View all Booking Calendar Contact Form vulnerabilities

At a glance

CVE-2026-6810 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Booking Calendar Contact Form WordPress plugin, affecting versions <= 1.2.63. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.64; sites on affected versions should update now. Disclosed April 2026, reported by Md. Moniruzzaman Prodhan (NomanProdhan).

Vulnerability Overview

The Booking Calendar Contact Form plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 1.2.63 via the dex_bccf_admin_int_calendar_list.inc.php file due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with Subscriber-level access and above, to takeover other user's calendars and view user data associated with the calendar.

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 Contact Form <= 1.2.63 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 Contact Form the fix is 1.2.64: builds <= 1.2.63 are affected, anything from 1.2.64 onward is not.

Remediation

Update to version 1.2.64, 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 Contact Form 1.2.64 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-6810https://www.wordfence.com/threat-intel/vulnerabilities/id/a3977d10-239d-4b83-ab0c-ad165485498dhttps://nvd.nist.gov/vuln/detail/CVE-2026-6810

Related records

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