# CVE-2023-5204: AI ChatBot <= 4.8.9 - Unauthenticated SQL Injection via qc_wpbo_search_response

> Unauthenticated attackers can exploit SQL injection in the AI ChatBot plugin to extract sensitive database information.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Oct 2023
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-xjgr-47gv-2g9p

## What is CVE-2023-5204?

CVE-2023-5204 is a critical SQL injection vulnerability in quantumcloud WPBot – AI ChatBot for Live Support, Lead Generation, AI Services, published on 19 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ChatBot plugin for WordPress is vulnerable to SQL Injection via the $strid parameter in versions up to, and including, 4.8.9 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query.  This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2023-5204?

It affects 1 product.


Products: Quantumcloud Wpbot.

## How do I fix CVE-2023-5204?

No fix has been published for CVE-2023-5204 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-5204 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5204 exists.

Public exploit code:

- AI ChatBot <= 4.8.9 - Unauthenticated SQL Injection via qc_wpbo_search_response (github_poc): https://github.com/RandomRobbieBF/CVE-2023-5204
- WordPress AI ChatBot (WPBot) <= 4.8.9 - SQL Injection (nuclei): http/cves/2023/CVE-2023-5204.yaml

## Other vulnerabilities in quantumcloud WPBot – AI ChatBot for Live Support, Lead Generation, AI Services

- [CVE-2023-1650](https://insights.sbomify.com/CVE-2023-1650/): ChatBot < 4.4.7 - Unauthenticated PHP Object Injection (critical 9.8)
- [CVE-2023-5212](https://insights.sbomify.com/CVE-2023-5212/): Path traversal in WPBot – AI ChatBot for Live Support, Lead Generation, AI Services (critical 9.6)
- [CVE-2023-5241](https://insights.sbomify.com/CVE-2023-5241/): Path traversal in WPBot – AI ChatBot for Live Support, Lead Generation, AI Services (critical 9.6)
- [CVE-2024-22309](https://insights.sbomify.com/CVE-2024-22309/): WordPress ChatBot Plugin <= 5.1.0 is vulnerable to PHP Object Injection (high 8.7)
- [CVE-2023-48741](https://insights.sbomify.com/CVE-2023-48741/): WordPress ChatBot Plugin <= 4.7.8 is vulnerable to SQL Injection (high 7.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-5204 and fix it if it is affected.

What it is: CVE-2023-5204 is a critical SQL injection vulnerability in quantumcloud WPBot – AI ChatBot for Live Support, Lead Generation, AI Services, published on 19 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-5204 exists.

Affected product: quantumcloud WPBot – AI ChatBot for Live Support, Lead Generation, AI Services. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-5204/ (Markdown: https://insights.sbomify.com/CVE-2023-5204/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-5204
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-5204
- OSV: https://osv.dev/vulnerability/CVE-2023-5204

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-5204/
Summaries are generated and may contain mistakes; the official description above is the record.