WPBot <= 8.5.6 - Missing Authorization to Unauthenticated Arbitrary Chat Session Deletion via 'userid' Parameter
Strategic Overview
- Status
- Patched in 8.5.7
- Affected Version
<= 8.5.6- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-15106
At a glance
CVE-2026-15106 is a medium-severity Missing Authorization vulnerability in the WPBot WordPress plugin, affecting versions <= 8.5.6. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 8.5.7; sites on affected versions should update now. Disclosed July 2026, reported by Wordfence PRISM.
Vulnerability Overview
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 unauthenticated attackers to delete arbitrary chat session records from the wpbot_user and wpbot_conversation tables, including chat history and conversation logs, by supplying a crafted userid value.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in WPBot <= 8.5.6 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WPBot the fix is 8.5.7: builds <= 8.5.6 are affected, anything from 8.5.7 onward is not.
Remediation
Update to version 8.5.7, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WPBot 8.5.7 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WPBot – AI ChatBot for Live Support, Lead Generation, AI Services
- 9.8CVE-2024-22309: ChatBot <= 5.1.0 PHP Object Injection
CVE-2024-22309 - 9.8CVE-2023-5204: AI ChatBot <= 4.8.9 SQL Injection
CVE-2023-5204 - 9.8CVE-2023-1650: ChatBot <= 4.4.6 PHP Object Injection
CVE-2023-1650 - 9.6CVE-2023-5241: AI ChatBot and 4.9.2 - Authenticated (Subscriber+)
CVE-2023-5241 - 9.6CVE-2023-5212: AI ChatBot and 4.9.2- Authenticated (Subscriber+)
CVE-2023-5212 - 8.8CVE-2025-26932: ChatBot <= 6.3.5 Local File Inclusion
CVE-2025-26932 - 7.5CVE-2026-32499: WPBot SQL Injection
CVE-2026-32499 - 7.2CVE-2026-83593: WPBot <= 8.7.3 Stored Cross-Site Scripting
CVE-2026-83593
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C