CVE-2023-5254

AI ChatBot <= 4.8.9 - Unauthenticated Sensitive Information Exposure via qcld_wb_chatbot_check_user

2023-10-11 00:00
Marco Wotschka

Strategic Overview

Status
Patched in 4.9.1
Affected Plugin
WPBot – AI ChatBot for Live Support, Lead Generation, WordPress Automation, AI Services
Affected Version
<= 4.8.9
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2023-5254
View all WPBot – AI ChatBot for Live Support, Lead Generation, WordPress Automation, AI Services vulnerabilities

At a glance

CVE-2023-5254 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WPBot WordPress plugin, affecting versions <= 4.8.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 4.9.1; sites on affected versions should update now. Disclosed October 2023, reported by Marco Wotschka.

Vulnerability Overview

The ChatBot plugin for WordPress is vulnerable to Sensitive Information Exposure in versions up to, and including, 4.8.9 via the qcld_wb_chatbot_check_user function. This can allow unauthenticated attackers to extract sensitive data including confirmation as to whether a user name exists on the site as well as order information for existing users.

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 <= 4.8.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 4.9.1: builds <= 4.8.9 are affected, anything from 4.9.1 onward is not.

Remediation

Update to version 4.9.1, 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 4.9.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-5254https://www.wordfence.com/threat-intel/vulnerabilities/id/d897daf8-5320-4546-9a63-1d34a15b2a58https://nvd.nist.gov/vuln/detail/CVE-2023-5254

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C