CVE-2026-12111

Appointment Booking Calendar <= 1.4.01 - Authenticated (Contributor+) Sensitive Information Exposure via 'id' Parameter

2026-06-17 18:14
Chloe Chamberland

Strategic Overview

Status
Patched in 1.4.02
Affected Version
<= 1.4.01
CVSS
4.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2026-12111
View all Appointment Booking Calendar vulnerabilities

At a glance

CVE-2026-12111 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Appointment Booking Calendar WordPress plugin, affecting versions <= 1.4.01. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 1.4.02; sites on affected versions should update now. Disclosed June 2026, reported by Chloe Chamberland.

Vulnerability Overview

The Appointment Booking Calendar plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 1.4.01. This is due to insufficient authorization and missing per-calendar ownership checks in the cpabc_appointments_calendar_load2() function, which is reachable via the cpabc_calendar_load2=1 query parameter in wp-admin and only checks is_admin() && current_user_can('edit_posts'), a capability available to Contributor-level users and above. This makes it possible for authenticated attackers with Contributor-level access and above to supply an arbitrary calendar ID via the id parameter and extract customer booking information, including email addresses, names, phone numbers, booking times, and comments, from any calendar managed by the plugin.

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-200: Exposure of Sensitive Information to an Unauthorized Actor

Appointment Booking Calendar <= 1.4.01 carries this weakness at edit_posts, and reaching it takes an account at Contributor level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Appointment Booking Calendar the fix is 1.4.02: builds <= 1.4.01 are affected, anything from 1.4.02 onward is not.

Remediation

Update to version 1.4.02, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Appointment Booking Calendar 1.4.02 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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