dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-6810

MEDIUM · 5.3 CVSS v3.1 Published 2026-04-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Booking Calendar Contact Form WordPress plugin versions up to 1.2.63 contains an Insecure Direct Object Reference vulnerability in dex_bccf_admin_int_calendar_list.inc.php. The plugin fails to validate that the user requesting access to a calendar actually owns that calendar, allowing any authenticated user with Subscriber-level permissions to access or takeover other users' calendars and view associated user data by manipulating a user-controlled key parameter.

MitigationUpdate the Booking Calendar Contact Form plugin to version 1.2.64 or later. If immediate update is not possible, implement supplemental access control validation in the affected file to verify calendar ownership before serving calendar data.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the Booking Calendar Contact Form plugin is installed
    Navigate to WordPress admin dashboard, go to Plugins > Installed Plugins, and locate 'Booking Calendar Contact Form' in the list
    Affected if the plugin is not installed or not found in the plugin list
  2. Check the installed plugin version
    In the Plugins list, look at the version number displayed beneath the plugin name 'Booking Calendar Contact Form', or check the plugin's main PHP file header for the Version field
    Affected if the version number is 1.2.63 or lower (any version up to and including 1.2.63)
  3. Verify the vulnerable file exists
    Check for the existence of dex_bccf_admin_int_calendar_list.inc.php in the plugin directory (typically wp-content/plugins/booking-calendar-contact-form/)
    Affected if the file exists in the plugin directory and the plugin version is 1.2.63 or lower
  4. Confirm authenticated user access is possible
    Log in with a user account that has Subscriber-level permissions and attempt to access calendar-related functionality or check if the plugin exposes any calendar-related endpoints accessible to authenticated users
    Affected if the WordPress site allows authenticated user registrations and the plugin is installed at a vulnerable version

You are affected if the Booking Calendar Contact Form plugin is installed at version 1.2.63 or lower, as any authenticated subscriber-level user could manipulate calendar access through the vulnerable file.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Booking Calendar Contact Form plugin to version 1.2.64 or later. If immediate update is not possible, implement supplemental access control validation in the affected file to verify calendar ownership before serving calendar data.

Recommended fix Moderate confidence

Booking Calendar Contact Form version 1.2.64 or latest available release

  1. Log in to WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Locate the 'Booking Calendar Contact Form' plugin
  4. Check if an update is available (version 1.2.64 or higher)
  5. If update available, click 'Update Now' to install the fixed version
  6. If no update appears in WordPress, manually download the latest version from plugins.trac.wordpress.org and upload via Plugins > Add New > Upload Plugin
  7. After updating, verify the plugin is running version 1.2.64 or higher

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-6810 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-6810 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data