CVE-2023-24415

ChatBot <= 4.2.8 - Cross-Site Request Forgery to Stored Cross-Site Scripting and Settings Reset

2023-01-27 00:00
Rafshanzani Suhada

Strategic Overview

Status
Patched in 4.2.9
Affected Plugin
WPBot – AI ChatBot for Live Support, Lead Generation, WordPress Automation, AI Services
Affected Version
<= 4.2.8
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2023-24415
View all WPBot – AI ChatBot for Live Support, Lead Generation, WordPress Automation, AI Services vulnerabilities

At a glance

CVE-2023-24415 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WPBot WordPress plugin, affecting versions <= 4.2.8. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.2.9; sites on affected versions should update now. Disclosed January 2023, reported by Rafshanzani Suhada.

Vulnerability Overview

The ChatBot plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.2.8. This is due to missing or incorrect nonce validation on the 'qcld_wb_chatbot_save_options' function. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page (via the 'wp_chatbot_position_x' and 'wp_chatbot_position_y' parameters). This is performed via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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.

CWE-352: Cross-Site Request Forgery (CSRF)

WPBot <= 4.2.8 carries this weakness at qcld_wb_chatbot_save_options, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WPBot the fix is 4.2.9: builds <= 4.2.8 are affected, anything from 4.2.9 onward is not.

Remediation

Update to version 4.2.9, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WPBot: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPBot 4.2.9 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-24415https://www.wordfence.com/threat-intel/vulnerabilities/id/04a79a78-a6d3-40ef-9b26-8e2e00534b7ahttps://nvd.nist.gov/vuln/detail/CVE-2023-24415

Related records

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