CVE-2024-0453

AI ChatBot <= 5.3.4 - Missing Authorization via openai_file_delete_callback

2024-05-21 00:00
Francesco Carlucci

Strategic Overview

Status
Patched in 5.3.6
Affected Plugin
WPBot – AI ChatBot for Live Support, Lead Generation, WordPress Automation, AI Services
Affected Version
<= 5.3.4
CVSS
5.0Medium
Weakness type
CWE-284 · Improper Access Control
CVE
CVE-2024-0453
View all WPBot – AI ChatBot for Live Support, Lead Generation, WordPress Automation, AI Services vulnerabilities

At a glance

CVE-2024-0453 is a medium-severity Improper Access Control vulnerability in the WPBot WordPress plugin, affecting versions <= 5.3.4. It carries a CVSS score of 5.0 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 5.3.6; sites on affected versions should update now. Disclosed May 2024, reported by Francesco Carlucci.

Vulnerability Overview

The AI ChatBot plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the openai_file_delete_callback function in all versions up to, and including, 5.3.4. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete files from a linked OpenAI account.

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 interaction from a victim user.

CWE-284: Improper Access Control

Reaching this weakness in WPBot <= 5.3.4 takes a caller who can reach the endpoint. Improper access control means the code decides what a caller may do using something other than their actual permissions, so the decision can be wrong without any check appearing to be missing.

Whoever can shape the request decides the answer, so the protected action runs for callers the code never meant to allow. For WPBot the fix is 5.3.6: builds <= 5.3.4 are affected, anything from 5.3.6 onward is not.

Remediation

Update to version 5.3.6, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WPBot 5.3.6 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-0453https://www.wordfence.com/threat-intel/vulnerabilities/id/7e0ef4a5-42d7-4cea-b19f-51917e3ee55fhttps://nvd.nist.gov/vuln/detail/CVE-2024-0453

Related records

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