EUVD-2026-51934
GHSA-xqfh-qj3w-mr75
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Network-accessible unauthenticated AJAX with no conditions warrants AV:N/AC:L/PR:N; I:L added because attacker actively dispatches unauthorized API requests on the owner's behalf, not merely reads data.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
5DescriptionCVE.org
The AI ChatBot for WooCommerce WordPress plugin before 4.8.4 does not perform any authorization or nonce check on one of its AJAX actions, allowing unauthenticated users to abuse the site owner's stored third-party API key to send requests billed to the owner's account and, when an optional feature is enabled, to retrieve indexed knowledge-base content.
AnalysisAI
Unauthenticated API abuse in the AI ChatBot for WooCommerce WordPress plugin (all versions before 4.8.4) permits any remote visitor to trigger a backend AJAX action with no authorization check or nonce validation, causing the plugin to forward requests to the site owner's stored third-party AI API credentials - generating charges billed directly to the owner's account. A publicly available exploit exists per WPScan, though EPSS sits at 0.15% (5th percentile), indicating limited current automated exploitation; this CVE is not listed in the CISA KEV catalog. When the plugin's optional knowledge-base indexing feature is enabled, the same unprotected endpoint additionally exposes indexed site content to unauthenticated retrieval, introducing a confidentiality dimension alongside the financial abuse risk.
Technical ContextAI
The plugin registers a WordPress AJAX action handler reachable via wp-admin/admin-ajax.php that proxies user requests to a third-party AI API (such as an LLM provider) using credentials stored in the WordPress options table. Standard WordPress AJAX security requires both a nonce (anti-CSRF token via check_ajax_referer()) and a capability check (current_user_can()) before processing sensitive actions; this plugin omits both, meaning the action is registered under the wp_ajax_nopriv_ hook and is fully accessible without authentication. CWE-284 (Improper Access Control) is the root cause: no gate exists between the public request and the privileged backend operation. CPE data (cpe:2.3:a:unknown:ai_chatbot_for_woocommerce:*:*:*:*:*:*:*:*) covers all versions below 4.8.4. The optional knowledge-base feature appears to implement retrieval-augmented generation (RAG) content indexing, and its exposure through the same unprotected endpoint adds a secondary information disclosure vector.
RemediationAI
Update the AI ChatBot for WooCommerce plugin to version 4.8.4 or later immediately; this is the vendor-released patch confirmed by WPScan (https://wpscan.com/vulnerability/81ab9ecd-5d7b-4d10-b255-65af869c46e2/). If patching cannot occur immediately, deactivate the plugin entirely to eliminate the exposed AJAX endpoint. After patching, rotate any third-party AI API keys previously stored in the plugin's configuration - any key in use during the exposure window should be considered compromised for billing purposes; revoke and reissue from the API provider's dashboard. If the optional knowledge-base feature was enabled, treat indexed content as potentially disclosed and review what was indexed. WAF rules blocking unauthenticated POST requests to wp-admin/admin-ajax.php with the affected action name may reduce exposure but risk false positives against legitimate plugin functionality and are not a substitute for patching.
Same weakness CWE-284 – Improper Access Control
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today