Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft link with malicious new_kb_config JSON
-
DeliveryLure Editor/Admin to click
-
ExploitConfig merged into KB style block
-
ExecutionUnescaped value breaks out of <style>
-
ImpactScript executes in privileged session
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a request that supplies epkb_fe_reload_mode=on against a knowledge base article page, carrying an attacker-controlled new_kb_config JSON blob (notably the article-mobile-break-point-v2 key and other config keys interpolated into the <style> element), which is merged over the stored KB configuration and emitted without escaping (minify_css() does not strip <, > or /). The decisive limiting factor is that the injected script only executes for a logged-in user with Editor-level access or above holding the manage_categories capability, or an Administrator, AND that user must be tricked into clicking the crafted link (UI:R) - so a visitor or anonymous reader cannot be targeted, materially reducing realistic impact. Affects default behavior of versions up to and including 17.214.0. |
| Impact | This is a genuine but lower-tier priority - a reflected XSS (CWE-79) rated CVSS 6.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) with the vuln.today decision label 'this_month' rather than act_now/emergency. The vector signals network reach, low complexity and no attacker authentication (PR:N), but it is gated by UI:R: exploitation requires tricking a victim into clicking a crafted link. The single most important limiting signal is in the description, not the CVSS: the injected script only executes in the browser of a user who already holds Editor-level-or-above privileges (manage_categories capability) or Administrator - so the victim pool is small and privileged, which sharply narrows real-world exploitability despite the 'unauthenticated attacker' framing. There is no CISA KEV listing and no EPSS value supplied, and no confirmed working exploit code is provided in the input - only the Wordfence advisory and WordPress trac source/changeset links - so exploitation status is 'no public exploit identified at time of analysis.' Signals are internally consistent (no CVSS-vs-description conflict), but the absence of EPSS/KEV plus the privileged-victim requirement together point to this being a real-but-not-urgent issue suitable for routine patching rather than emergency response. |
| Exploit ScenarioDerived | An unauthenticated attacker crafts a link to a knowledge base article page that appends epkb_fe_reload_mode=on and a malicious new_kb_config JSON blob (e.g. via the article-mobile-break-point-v2 key), whose value is concatenated unescaped into a <style> element. The attacker sends this link to a site Editor or Administrator; when that privileged user clicks it, the injected script executes in their authenticated browser session. No confirmed working exploit code is provided in the input - only the Wordfence advisory and trac source references. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 28, 2026
Reflected cross-site scripting in the Echo Knowledge Base - Documentation, FAQs, Chat & Smart Search plugin for WordPress (versions up to and including 17.214.0) lets a remote attacker place arbitrary script in a knowledge base article page by supplying an epkb_fe_reload_mode=on request that carries a crafted new_kb_config JSON blob, whose values are merged over the stored KB configuration and concatenated unescaped into a <style> element. Rated CVSS 6.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) and tracked as CWE-79, the practical ceiling is limited: the payload only executes in the browser of a logged-in user with Editor-level access or above holding the manage_categories capability, or an Administrator, and that user must be tricked into clicking the crafted link (UI:R), so anonymous visitors and ordinary readers cannot be targeted. No public exploit code was identified in the supplied intelligence and there is no CISA KEV entry; the vuln.today decision label is 'this_month' rather than act_now or emergency. Vulnerability details were reported by Wordfence and cross-referenced by ENISA as EUVD-2026-111818.
RemediationAI
Upgrade the Echo Knowledge Base plugin past 17.214.0: the WordPress.org changeset for class-epkb-frontend-editor.php (https://plugins.trac.wordpress.org/changeset/3727663/echo-knowledge-base/trunk/includes/admin/editor/class-epkb-frontend-editor.php) and the tag comparison between 17.214.0 and 17.311.0 (https://plugins.trac.wordpress.org/changeset?reponame=&new=3727647%40echo-knowledge-base%2Ftags%2F17.311.0&old=3672811%40echo-knowledge-base%2Ftags%2F17.214.0) show the upstream fix landing in that code; because a specific patched release number is not explicitly declared in the supplied advisory data, verify the plugin's current version on wordpress.org and apply the latest release, treating 17.311.0 or later as the practical target, then confirm the changelog via the Wordfence advisory referenced above. No vendor-documented workaround is included in the available sources; the described trigger requires a request carrying epkb_fe_reload_mode=on together with a new_kb_config JSON blob against a knowledge base article page, so a temporary virtual-patch or WAF rule rejecting requests that combine that parameter with new_kb_config (or that contain angle brackets in those values) reduces exposure, at the cost of blocking the legitimate frontend preview feature, and restriction of article editing/preview to trusted administrators limits who can be targeted through UI:R but does not remove the injection path.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw sits in a WordPress plugin's styling pipeline. EPKB_Frontend_Editor::fe_preview_config() handles the frontend preview of knowledge base configuration; when a request supplies epkb_fe_reload_mode=on, an attacker-controlled JSON blob (new_kb_config) is merged over the stored KB configuration. Several of those config values - notably article-mobile-break-point-v2, along with other keys interpolated into the stylesheet - are then concatenated directly into a stylesheet emitted inside a literal <style> element. The helper minify_css() in EPKB_Utilities does not strip <, >, or /, so a value carrying a closing </style> sequence or HTML markup breaks out of the style context and is rendered as markup, which is the classic CWE-79 reflected-XSS root cause: missing input sanitization combined with missing output escaping for a non-HTML output context. The tainted values flow through EPKB_Articles_Setup (class-epkb-articles-setup.php lines 131 and 319), EPKB_Frontend_Editor (class-epkb-frontend-editor.php lines 848 and 1072), EPKB_Utilities (class-epkb-utilities.php line 836) and EPKB_Layouts_Setup (class-epkb-layouts-setup.php line 45) on every knowledge base article page view where the reload parameter is present. Because the request vector is AV:N/PR:N and the code path is the plugin's default article rendering, no authentication is needed to deliver the payload; the constraint is on the victim side, since the injected script executes only in the session of an authenticated user at Editor level or above (manage_categories) or an Administrator, and only after that user follows a crafted link (UI:R, scope changed S:C).
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Unauthenticated attacker crafts the link (PR:N) but a privileged victim must click it (UI:R); XSS executing in the browser is a scope change (S:C) with limited C/I and no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Echo Knowledge Base - Documentation, FAQs, Chat & Smart Search plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the 'new_kb_config' parameter (specifically the article-mobile-break-point-v2 key, among other config keys interpolated into the <style> element) in versions up to, and including, 17.214.0 This is due to insufficient input sanitization and output escaping in EPKB_Frontend_Editor::fe_preview_config() and EPKB_Articles_Setup: on every knowledge base article page view, when the request supplies epkb_fe_reload_mode=on, an attacker-controlled JSON blob is merged over the stored KB configuration and several values are concatenated directly into a stylesheet emitted inside a literal <style> element without escaping (minify_css() does not strip <, > or /). This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user (with Editor-level access or above, holding the manage_categories capability, or an Administrator) into performing an action such as clicking on a specially crafted link.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-111818
GHSA-7f9m-hhf7-j63p
NVD
CVE.org
EPSS
Exploit-DB