WPBot <= 8.5.9 - Unauthenticated Sensitive Information Exposure in 'wpbot_send_email_transcript' AJAX Action
Strategic Overview
- Status
- Patched in 8.6.0
- Affected Version
<= 8.5.9- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-16773
At a glance
CVE-2026-16773 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WPBot WordPress plugin, affecting versions <= 8.5.9. 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.6.0; 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 Sensitive Information Exposure in all versions up to, and including, 8.5.9 via the wpbot_send_email_transcript_free. This makes it possible for unauthenticated attackers to exfiltrate full chat transcripts and associated user PII — including names, email addresses, and phone numbers — stored in the wpbot_user and wpbot_conversation tables to an attacker-controlled email address.
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-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in WPBot <= 8.5.9 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For WPBot the fix is 8.6.0: builds <= 8.5.9 are affected, anything from 8.6.0 onward is not.
Remediation
Update to version 8.6.0, 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.6.0 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