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-88905 Overview
CVE-2026-88905 affects the KeyWord Collector WordPress plugin through version 1.4. The plugin fails to perform authorization or nonce checks when saving its settings and does not escape output. Unauthenticated attackers can store malicious JavaScript that executes when an administrator opens the plugin's settings page or when a visitor loads a page displaying its output. The flaw is classified as a stored Cross-Site Scripting vulnerability [CWE-79].
Critical Impact
Unauthenticated attackers can inject persistent JavaScript into WordPress sites running the KeyWord Collector plugin, enabling administrator account takeover and site-wide compromise.
Affected Products
- KeyWord Collector WordPress plugin, all versions through 1.4
- WordPress sites with the plugin installed and activated
- Administrator sessions visiting the plugin settings page
Discovery Timeline
- 2026-10-11 - CVE-2026-88905 published to the National Vulnerability Database
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-88905
Vulnerability Analysis
The KeyWord Collector plugin exposes a settings-save endpoint without authentication or Cross-Site Request Forgery (CSRF) protection. Any unauthenticated request can modify plugin configuration values. The stored values are later rendered in administrative pages and front-end output without HTML escaping. This combination transforms a missing authorization defect into a stored Cross-Site Scripting (XSS) condition reachable by remote attackers.
When an administrator loads the settings screen, the injected payload executes in the context of the authenticated session. The script inherits administrator privileges and can create new users, modify plugin or theme files, or exfiltrate session cookies. Visitors loading pages that display the plugin output are also exposed to the stored payload.
Root Cause
The root cause is twofold. First, the settings handler lacks a current_user_can() capability check and a wp_verify_nonce() call. Second, the output path does not apply esc_html(), esc_attr(), or wp_kses() before rendering stored values. Both the input and output layers fail, allowing untrusted data to reach the browser as executable script.
Attack Vector
Exploitation requires only network access to the WordPress site. An attacker sends a crafted HTTP POST request to the plugin's settings save endpoint with a JavaScript payload embedded in a configuration field. The payload persists in the database. Execution occurs when an administrator opens the settings page or when any visitor loads a public page that renders the stored value. User interaction from the victim administrator or site visitor is required for script execution.
Technical details are described in the WPScan Vulnerability Report.
Detection Methods for CVE-2026-88905
Indicators of Compromise
- Unexpected <script>, onerror, or onload strings stored in the wp_options table entries belonging to the KeyWord Collector plugin
- Creation of new WordPress administrator accounts without a corresponding audit trail
- Outbound HTTP requests from administrator browser sessions to unknown domains after visiting the plugin settings page
- Unauthenticated POST requests to the plugin's settings endpoint in web server access logs
Detection Strategies
- Inspect plugin option rows for HTML or JavaScript content using database queries against wp_options
- Review WordPress audit logs for configuration changes to KeyWord Collector settings from unauthenticated or anonymous sources
- Deploy Web Application Firewall (WAF) rules that flag POST requests containing script tags targeting plugin admin endpoints
Monitoring Recommendations
- Monitor web server logs for POST requests to WordPress admin-ajax or plugin-specific endpoints lacking valid session cookies
- Alert on modifications to WordPress administrator user accounts and role assignments
- Correlate browser-side Content Security Policy (CSP) violation reports with administrator activity on plugin settings pages
How to Mitigate CVE-2026-88905
Immediate Actions Required
- Deactivate and remove the KeyWord Collector plugin until a patched version is released
- Audit the wp_options table and plugin configuration for stored script payloads and remove any injected content
- Rotate administrator credentials and invalidate active WordPress sessions
- Review recently created user accounts and remove unauthorized administrators
Patch Information
No fixed version is listed in the advisory as of the last NVD update on 2026-10-13. The vulnerability affects all versions through 1.4. Monitor the WPScan Vulnerability Report for patch availability.
Workarounds
- Remove the plugin entirely until a vendor patch is available
- Restrict access to WordPress admin paths using IP allow-listing at the web server or WAF layer
- Deploy a Content Security Policy that blocks inline script execution in the WordPress admin interface
- Apply WAF signatures that reject requests containing script tags or event handler attributes to plugin endpoints
# Example nginx rule to block script payloads to plugin endpoints
location ~* /wp-content/plugins/keyword-collector/ {
if ($request_method = POST) {
if ($request_body ~* "(<script|onerror=|onload=|javascript:)") {
return 403;
}
}
}
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

