EUVD-2026-46157
GHSA-wxfw-phg9-mqvh
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Handler is network-accessible, subscriber account (PR:L) is the sole prerequisite, with integrity-only impact on plugin configuration and no confidentiality or availability exposure.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
5DescriptionCVE.org
The WPBot WordPress plugin before 8.2.0 does not perform a capability or nonce check in one of its retrieval-augmented-generation settings handlers, allowing authenticated users with subscriber-level access to modify the WPBot WordPress plugin before 8.2.0's configuration.
AnalysisAI
Subscriber-level users on WordPress sites running WPBot before 8.2.0 can modify the plugin's retrieval-augmented-generation (RAG) configuration without authorization, because the relevant settings handler performs neither a WordPress capability check nor a nonce validation. A publicly available proof-of-concept lowers the exploitation bar significantly, making this actionable for any low-skill attacker who holds or can self-register a subscriber account on the target site. No public exploit identified at time of analysis by CISA KEV, but POC availability combined with low access requirements makes remediation a priority for sites with open user registration.
Technical ContextAI
WPBot is a WordPress chatbot plugin that incorporates retrieval-augmented generation (RAG) functionality, integrating AI-driven content retrieval into chat responses. The root cause is CWE-862 (Missing Authorization): a server-side AJAX or REST handler responsible for writing RAG settings fails to call WordPress's capability-check functions (e.g., current_user_can('manage_options')) and omits nonce verification to prevent cross-site request forgery. In WordPress's privilege model, subscriber is the default role granted to self-registered users with no administrative rights; the absence of a gate means any authenticated session - regardless of role - can invoke this handler. The CPE string cpe:2.3:a:unknown:wpbot:*:*:*:*:*:*:*:* reflects that NVD has not yet resolved the vendor namespace, though the product is the WPBot plugin distributed through the WordPress.org ecosystem. All versions in the range 0 through below 8.2.0 are within scope.
RemediationAI
Update the WPBot plugin to version 8.2.0 or later, where the vendor has introduced the missing capability and nonce checks in the RAG settings handler; this is the definitive fix confirmed by the WPScan advisory at https://wpscan.com/vulnerability/a6839476-95bf-4785-b128-1e3bc8603ddc/. As an immediate compensating control before patching, disable open user registration (WordPress Admin → Settings → General → uncheck 'Anyone can register') to prevent new subscriber-level accounts from being created - note this does not protect against existing subscriber accounts already on the site. If the RAG feature of WPBot is not in use, consider disabling it within the plugin settings to reduce the exposed handler surface, though the specific toggle depends on plugin version. As a last resort, deactivating the WPBot plugin entirely eliminates the attack surface at the cost of chatbot functionality. Audit existing subscriber accounts for unexpected or self-registered users as a follow-on hygiene step.
The ChatBot plugin for WordPress is vulnerable to SQL Injection via the $strid parameter in versions up to, and includin
The AI ChatBot WordPress plugin before 4.4.7 unserializes user input from cookies via an AJAX action available to unauth
The AI ChatBot WordPress plugin before 4.4.9 does not have authorisation and CSRF in a function hooked to init, allowing
The AI ChatBot WordPress plugin before 4.4.5 does not escape most of its settings before outputting them back in the das
The AI ChatBot for WordPress is vulnerable to Directory Traversal in versions up to, and including, 4.8.9 as well as 4.9
The AI ChatBot plugin for WordPress is vulnerable to Arbitrary File Deletion in versions up to, and including, 4.8.9 as
The AI ChatBot WordPress plugin before 4.4.9 does not have authorisation and CSRF in the AJAX action responsible to upda
The ChatBot plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 4.8.9
Cross-Site Request Forgery (CSRF) vulnerability in QuantumCloud AI ChatBot plugin <= 4.7.8 versions. Rated high severity
The AI ChatBot WordPress plugin before 4.7.8 does not sanitise and escape some of its settings, which could allow high p
The AI ChatBot WordPress plugin before 4.7.8 does not sanitise and escape some of its settings, which could allow high p
The AI ChatBot WordPress plugin before 4.6.1 does not adequately escape some settings, allowing high-privilege users suc
Same weakness CWE-862 – Missing Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today