Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconVisit public WordPress page
-
DeliveryExtract WPBot nonce from page source
-
ExploitPOST crafted conversation payload with script
-
InstallPayload stored in chat session database
-
C2Admin opens chat session review panel
-
ExecuteInjected script executes in admin browser
-
ImpactSession hijacked or site compromised
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 | No special conditions are required beyond the WPBot plugin being installed and active with chat sessions enabled on a WordPress site. The nonce that nominally gates the submission endpoint is publicly embedded in every page by the plugin itself, meaning any unauthenticated visitor can retrieve a valid nonce and submit conversation data without any account, credential, or elevated access. Exploitation is limited only by the need for a victim (typically an administrator) to subsequently visit the page or admin panel section where the injected conversation is rendered - the injection step itself requires no user interaction. Versions 8.7.3 and below are affected; the vulnerability does not require any non-default configuration. |
| Impact | The CVSS 3.1 vector provided (AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N) scores to approximately 6.7, not the stated 7.2 - a minor scoring discrepancy worth noting but not materially affecting triage. More substantively, the UI:N designation is debatable: for the stored XSS to execute against a victim, that victim must navigate to a page containing the injected payload, which is conventionally UI:R. The scope-change designation (S:C) is appropriate because successful XSS executes in a victim's browser context, potentially enabling session hijacking, admin credential theft, or site defacement affecting users beyond the immediate vulnerable component. No KEV listing and no public exploit confirm this is not currently under active mass exploitation. However, the nonce-bypass mechanism is simple to exploit - any attacker who reads the page source and submits a crafted POST request can permanently inject scripts. The primary real-world risk is stored XSS payloads targeting administrators who review chat session logs, potentially leading to full WordPress site compromise. |
| Exploit ScenarioDerived | An attacker visits any public-facing page of the target WordPress site, extracts the WPBot nonce embedded in the page source via wp_localize_script, and submits a crafted POST request to the chat session endpoint with the 'conversation' parameter containing a malicious JavaScript payload. The script is stored server-side and silently executes in the browser of any administrator who opens the chat session review panel, potentially stealing their session cookie and granting full administrative control of the WordPress site. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 09, 2026
Stored Cross-Site Scripting in the WPBot AI ChatBot WordPress plugin (QuantumCloud, all versions through 8.7.3) allows unauthenticated remote attackers to inject persistent JavaScript into pages viewed by site users and administrators. The critical design flaw is that the only access gate - a WordPress nonce - is rendered useless because it is embedded in every public-facing page via wp_localize_script, making it fully readable by any visitor. No public exploit code has been identified at time of analysis, but the low attack complexity and zero-authentication requirement make this a straightforward exploitation path for opportunistic attackers targeting WordPress sites.
RemediationAI
Update to the first version beyond 8.7.3 as published in the WordPress plugin repository - the exact patched release version is not confirmed in the provided data, so consult the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/710fb372-4b7e-43e3-86a7-417143536f43) and the WordPress.org plugin changelog for the confirmed fix version. If an immediate update is not possible, the most effective compensating control is to disable the WPBot chat sessions feature entirely from the plugin settings, which prevents conversation data from being submitted and stored. Alternatively, a Web Application Firewall rule blocking requests to the chat session submission endpoint can limit exposure, though this may break legitimate chatbot functionality. Site owners should also audit existing stored chat conversations in the admin panel for signs of injected script tags indicating prior exploitation.
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 vulnerability resides in the plugin's chat session handling code, specifically the 'conversation' parameter processed by wpbot-chat-sessions.php (lines 564, 566, 708, 866) and functions.php (line 1922). WordPress nonces are cryptographic tokens designed to prevent CSRF attacks, but they are not secrets - they are routinely included in page source via wp_localize_script to allow JavaScript to make authenticated AJAX calls. When nonce verification is the sole access control gating a data-write endpoint, any unauthenticated visitor can extract a valid nonce from the page source and submit arbitrary input. The plugin fails to apply sufficient input sanitization before storage and output escaping before rendering, satisfying the CWE-79 (Improper Neutralization of Input During Web Page Generation) root cause. The CPE is cpe:2.3:a:quantumcloud:wpbot_-_ai_chatbot_for_live_support,_lead_generation,_ai_services:*:*:*:*:*:*:*:*, confirmed by the Wordfence threat intelligence report.
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:N/S:C/C:L/I:L/A:N
Stored XSS requires a victim to view the injected page (UI:R); nonce publicly exposed removes any privilege barrier (PR:N); scope changes to victim browser (S:C).
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The WPBot - AI ChatBot for Live Support, Lead Generation, AI Services plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'conversation' parameter in all versions up to, and including, 8.7.3 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The action is gated only by a nonce that is localized into every public-facing page via wp_localize_script, rendering the nonce check ineffective as an access control barrier for unauthenticated users.
Articles & Coverage 1
Executive ViewAI
WordPress sites running WPBot AI ChatBot (QuantumCloud, through version 8.7.3) are vulnerable to persistent JavaScript injection by unauthenticated attackers, affecting all site visitors and administrators. No public exploit identified at time of analysis, but the fundamental access control design flaw makes exploitation straightforward and likely to attract opportunistic attackers. With no vendor patch currently available, organizations must urgently choose between plugin removal and deploying temporary technical controls.
No vendor-released patch identified at time of analysis. Interim mitigations: immediately disable or remove the plugin; if business-critical, implement Content Security Policy headers to restrict inline script execution and WAF rules to detect and block stored-XSS patterns; audit all stored page content and database for existing injected scripts; enable continuous monitoring for unauthorized content modifications. Complete remediation requires vendor security patch upon release.
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-74688
GHSA-3ghv-v9gq-7ghq
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB