# CVE-2019-1010104: SQL injection in Quick Chat WordPress Plugin

> Attackers can execute SQL commands via crafted AJAX requests to access the database in the Quick Chat WordPress plugin.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 18 Jul 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gqmr-r75p-994g

## What is CVE-2019-1010104?

CVE-2019-1010104 is a critical SQL injection vulnerability in TechyTalk Quick Chat WordPress Plugin, published on 18 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

TechyTalk Quick Chat WordPress Plugin All up to the latest is affected by: SQL Injection. The impact is: Access to the database. The component is: like_escape is used in Quick-chat.php line 399. The attack vector is: Crafted ajax request.

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

## Which versions are affected by CVE-2019-1010104?

It affects 1 product.


Products: Techytalk Quick Chat.

## How do I fix CVE-2019-1010104?

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

## Is CVE-2019-1010104 being exploited?

There is no known exploitation of CVE-2019-1010104 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-1010104 and fix it if it is affected.

What it is: CVE-2019-1010104 is a critical SQL injection vulnerability in TechyTalk Quick Chat WordPress Plugin, published on 18 Jul 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-1010104 in the wild and no public exploit code.

Affected product: TechyTalk Quick Chat WordPress Plugin. 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-2019-1010104/ (Markdown: https://insights.sbomify.com/CVE-2019-1010104/index.md)
```

## Sources

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

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