What is the CVSS score of CVE-2026-15610?

CVE-2026-15610 has a CVSS 3.1 base score of 4.3 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N. EPSS exploitation probability: 0.2%.

WPBot CVE-2026-15610

EUVD-2026-44893 MEDIUM

Missing Authorization (CWE-862)

2026-07-16 Wordfence

GHSA-h524-vxvw-w455

WordPress Authentication Bypass Wordpress Plugin Wpbot Ai Chatbot For Live Support Lead Generation Ai Services Quantumcloud

4.3

CVSS 3.1 · Vendor: Wordfence

Severity by source

Vendor (Wordfence) PRIMARY

4.3 MEDIUM

AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

vuln.today AI

4.3 MEDIUM

Network exploitation requires only subscriber credentials (PR:L); no confidentiality breach or direct availability impact on the WordPress system itself justifies C:N and A:N.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Jul 16, 2026 - 09:07 vuln.today

CVE Published

Jul 16, 2026 - 07:51 cve.org

MEDIUM 4.3

DescriptionCVE.org

The WPBot - AI ChatBot for Live Support, Lead Generation, AI Services plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 8.5.6. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to trigger arbitrary re-embedding of stored RAG documents, modifying the rag_documents table and consuming the site owner's paid third-party AI API credits (OpenAI, Gemini, OpenRouter, or xAI).

AnalysisAI

Authorization bypass in the WPBot AI ChatBot plugin for WordPress (all versions ≤ 8.5.6) permits any subscriber-level authenticated user to invoke the plugin's RAG document re-embedding functionality without authorization, directly modifying the rag_documents database table and triggering calls to the site owner's paid AI APIs (OpenAI, Gemini, OpenRouter, or xAI). The root cause is a missing capability check in class-qcld-bot-rag.php, confirmed by Wordfence and traceable to specific code paths in qcld-wpwbot.php. No public exploit code or active exploitation (CISA KEV) has been identified at time of analysis, and the CVSS 4.3 Medium score reflects constrained direct security impact - though financial harm from API credit exhaustion represents the primary real-world risk.

Technical ContextAI

WPBot (CPE: cpe:2.3:a:quantumcloud:wpbot_-_ai_chatbot_for_live_support,_lead_generation,_ai_services:*:*:*:*:*:*:*:*) is a QuantumCloud WordPress plugin that implements Retrieval-Augmented Generation (RAG) to enable AI-powered chatbot responses using site-operator-provided documents. The vulnerable logic resides in includes/class-qcld-bot-rag.php (line 791 and line 27 across tags 8.4.9 and 8.5.5) and is registered in qcld-wpwbot.php (line 608). CWE-862 (Missing Authorization) identifies the root cause: the plugin exposes an action endpoint for re-embedding stored RAG documents but does not verify that the requesting user holds a capability sufficient to perform that privileged operation. Because embedding calls are proxied to third-party AI APIs (OpenAI, Gemini, OpenRouter, xAI) using site-owner API keys, unauthorized invocations directly consume paid API quota on behalf of the site owner.

RemediationAI

Update the WPBot plugin to version 8.5.7 or later; a fix was committed upstream per the WordPress plugin trac changeset (https://plugins.trac.wordpress.org/changeset?reponame=&old=3608558%40chatbot&new=3608558%40chatbot). Note that the exact patched release version is not independently confirmed from the provided data - verify the current version via the WordPress.org plugin repository before deploying. As a compensating control while patching, site administrators should audit and restrict subscriber-level user registration to prevent untrusted accounts from being created; this eliminates the attack surface without requiring downtime. Alternatively, administrators can temporarily revoke or rotate the AI API keys (OpenAI, Gemini, OpenRouter, xAI) configured in the plugin, which halts financial abuse but fully disables AI chatbot functionality. After patching, review API usage dashboards for each configured provider to identify any unauthorized credit consumption that occurred prior to remediation.