Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-108123 Overview
CVE-2026-108123 is an authorization bypass vulnerability in the WP Booking System – Booking Calendar plugin for WordPress. The flaw affects all plugin versions up to and including 2.1.0.3. The plugin fails to verify that a requesting user is authorized to read stored notification email bodies associated with booking records. Unauthenticated and low-privileged attackers can iterate booking_id and email_log_id parameters to disclose customer personally identifiable information (PII). Exposed data includes names, email addresses, phone numbers, free-form messages, and booking dates intended for administrator viewing only. The weakness maps to CWE-862: Missing Authorization.
Critical Impact
Attackers can enumerate stored booking notification emails and harvest customer PII from any WordPress site running vulnerable versions of the plugin.
Affected Products
- WP Booking System – Booking Calendar plugin for WordPress
- All versions through 2.1.0.3
- WordPress sites with Subscriber-level (or higher) authenticated users exposed to the issue via profile.php
Discovery Timeline
- 2026-10-17 - CVE-2026-108123 published to the National Vulnerability Database (NVD)
- 2026-10-19 - Last updated in NVD database
Technical Details for CVE-2026-108123
Vulnerability Analysis
The vulnerability resides in the plugin's administrative booking functions, specifically within includes/base/admin/booking/functions.php. The handler responsible for returning the stored notification email body executes without validating the caller's role or ownership of the referenced booking. The handler is registered to the admin_init hook. Because admin_init fires on profile.php—a wp-admin page accessible to any authenticated WordPress user—even Subscriber-level accounts reach the vulnerable code path. The handler accepts a booking_id and email_log_id from the request and returns the stored email content directly.
Root Cause
The root cause is missing authorization enforcement around a sensitive administrative action [CWE-862]. The plugin relies on the request reaching an admin-facing hook as an implicit trust boundary rather than performing an explicit current_user_can() capability check or validating a nonce tied to a privileged action. As a result, access control is absent for the email-log retrieval function referenced at lines 244 and 250 of the vulnerable file.
Attack Vector
The attack vector is network-based and requires no user interaction. An attacker with a Subscriber account—trivially obtained on sites that allow open registration—requests profile.php with the plugin's action parameters and iterates numeric booking_id and email_log_id values. Each successful request returns the rendered notification email body for a booking. Confidentiality impact is high; integrity and availability are not affected. The EPSS probability is listed at 0.318%.
The vulnerability manifests in the admin booking functions file. See the vendor source reference and the patch changeset #3750085 for implementation details.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-108123
Indicators of Compromise
- Repeated authenticated requests to /wp-admin/profile.php containing plugin-specific action parameters along with booking_id and email_log_id query values
- Sequential iteration patterns across booking_id or email_log_id values originating from a single low-privileged account
- Newly registered Subscriber accounts generating wp-admin traffic shortly after account creation
- Outbound exfiltration of HTML content containing customer email templates to attacker-controlled hosts
Detection Strategies
- Inspect web server and WordPress access logs for profile.php requests carrying booking-related parameters that would not appear in normal user profile activity
- Correlate request volume per authenticated session against a baseline; enumeration attempts generate anomalous request counts
- Deploy a Web Application Firewall (WAF) rule that flags admin_init-reachable endpoints invoked by non-administrator sessions
Monitoring Recommendations
- Enable verbose logging on the WordPress admin area and forward logs to a centralized analytics platform such as the Singularity Data Lake for retention and correlation
- Monitor user registration events and subsequent admin-area access by newly created accounts
- Alert on bursts of HTTP 200 responses from profile.php with query strings referencing plugin booking actions
How to Mitigate CVE-2026-108123
Immediate Actions Required
- Update the WP Booking System – Booking Calendar plugin to a version newer than 2.1.0.3 as soon as the fixed release is available from the vendor
- Disable open user registration on affected WordPress sites until patching is complete
- Audit existing Subscriber accounts and remove accounts that are unknown, inactive, or suspicious
- Review web server logs for prior enumeration of booking_id and email_log_id values and notify affected customers if PII was exposed
Patch Information
The vendor addressed the authorization gap in changeset #3750085. Administrators should install the patched release of the plugin via the WordPress plugin updater. Full details are documented in the Wordfence Vulnerability Report.
Workarounds
- Temporarily deactivate the WP Booking System – Booking Calendar plugin until the patched version is deployed
- Restrict access to /wp-admin/ by IP allowlist at the web server or WAF layer to block unauthenticated and Subscriber-level enumeration from the public internet
- Set WordPress to disallow new user self-registration (Settings → General → Membership) while the plugin remains vulnerable
- Apply a WAF rule that blocks requests to profile.php carrying booking_id or email_log_id parameters
# Example WAF-style guard (nginx) to block booking enumeration via profile.php
location = /wp-admin/profile.php {
if ($arg_booking_id) { return 403; }
if ($arg_email_log_id) { return 403; }
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

