Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-94167 Overview
CVE-2026-94167 is a reflected cross-site scripting (XSS) vulnerability in the Extend Themes Kubio AI Page Builder plugin for WordPress. The flaw stems from improper neutralization of user input during web page generation [CWE-79]. All versions of the kubio plugin up to and including 2.9.3 are affected. An attacker can craft a malicious URL that, when visited by an authenticated user, executes arbitrary JavaScript in the victim's browser session.
Because the CVSS vector includes a scope change (S:C), successful exploitation can affect resources beyond the vulnerable component, including the user's browser context and any accessible session data.
Critical Impact
Reflected XSS enables attackers to hijack administrator sessions, inject malicious content into WordPress admin pages, and pivot to full site compromise through plugin or theme modification.
Affected Products
- Extend Themes Kubio AI Page Builder (kubio) WordPress plugin
- All versions from initial release through 2.9.3
- WordPress sites with the vulnerable plugin installed and active
Discovery Timeline
- 2026-10-09 - CVE-2026-94167 published to NVD
- 2026-10-09 - Last updated in NVD database
Technical Details for CVE-2026-94167
Vulnerability Analysis
The vulnerability is a reflected XSS flaw in the Kubio AI Page Builder plugin. Reflected XSS occurs when a web application accepts user-supplied input and returns it in the HTTP response without proper encoding or sanitization. An attacker crafts a URL containing malicious JavaScript payloads and delivers it to a victim through phishing, forum posts, or social engineering.
When the victim clicks the link, the Kubio plugin processes the attacker-controlled parameter and reflects it into the rendered page. The browser executes the injected script in the context of the WordPress site. The scope change in the CVSS vector indicates that the injected code can affect components beyond the vulnerable plugin itself.
The EPSS score currently sits at the low end of the distribution, suggesting limited observed exploitation activity. However, XSS flaws in WordPress plugins are routinely weaponized once public details circulate.
Root Cause
The root cause is missing or insufficient output encoding of user-controlled input before it is embedded into the HTML response. The plugin fails to apply WordPress sanitization functions such as esc_html(), esc_attr(), or wp_kses() to one or more request parameters. This allows raw HTML and JavaScript to be reflected into the DOM.
Attack Vector
Exploitation requires user interaction (UI:R) and no privileges (PR:N). An attacker constructs a URL targeting the vulnerable Kubio endpoint with a JavaScript payload in a query parameter. The attacker delivers the URL to a WordPress user, typically an administrator or editor, through email or an external site. When the target visits the URL while authenticated, the injected script executes with the user's privileges and can perform actions such as creating new administrator accounts, exfiltrating session cookies, or modifying site content.
No verified public exploit code is available at this time. Technical details are documented in the Patchstack Vulnerability Report.
Detection Methods for CVE-2026-94167
Indicators of Compromise
- Unexpected <script> tags, javascript: URIs, or event handler attributes (onerror, onload) appearing in WordPress admin page responses
- HTTP requests to Kubio plugin endpoints containing URL-encoded JavaScript payloads such as %3Cscript%3E or %3Cimg%20onerror%3D
- Creation of unauthorized WordPress administrator accounts following access to Kubio pages
- Unexpected outbound requests from administrator browsers to attacker-controlled domains after visiting crafted URLs
Detection Strategies
- Deploy a web application firewall (WAF) with signatures for reflected XSS payloads targeting WordPress plugins
- Monitor web server access logs for GET and POST requests to /wp-content/plugins/kubio/ paths containing script-like characters
- Enable Content Security Policy (CSP) reporting to detect script execution from unexpected sources
- Review WordPress audit logs for anomalous administrative actions following external referral traffic
Monitoring Recommendations
- Alert on WordPress user role changes and new administrator account creation events
- Correlate browser-based telemetry with WordPress admin session activity to identify session hijacking attempts
- Track outbound HTTP requests from browsers accessing WordPress admin interfaces to flag data exfiltration
How to Mitigate CVE-2026-94167
Immediate Actions Required
- Identify all WordPress installations running the Kubio AI Page Builder plugin version 2.9.3 or earlier
- Apply the vendor-released patched version as soon as it becomes available through the WordPress plugin repository
- Restrict administrator and editor access to trusted networks and enforce multi-factor authentication on privileged accounts
- Educate privileged WordPress users to avoid clicking untrusted links while authenticated to the admin console
Patch Information
At the time of publication, the Patchstack advisory lists the vulnerability as present through version 2.9.3. Site operators should monitor the official Kubio plugin listing on the WordPress plugin directory for a fixed release and apply it immediately. Refer to the Patchstack Vulnerability Report for ongoing patch status.
Workarounds
- Deactivate and remove the Kubio AI Page Builder plugin until a patched version is installed
- Deploy a WAF rule set that blocks reflected XSS payload patterns targeting the plugin's parameters
- Implement a strict Content Security Policy that disallows inline scripts and limits script sources to trusted origins
- Use browser isolation or dedicated administrative workstations for WordPress admin tasks to limit payload impact
# Example WAF rule concept to block script tags in Kubio plugin requests
# (ModSecurity-style pseudocode - adapt to your WAF syntax)
SecRule REQUEST_URI "@contains /wp-content/plugins/kubio/" \
"chain,deny,status:403,id:1026094167,msg:'Potential XSS targeting Kubio plugin'"
SecRule ARGS "@rx (?i)(<script|javascript:|onerror=|onload=)"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

