# CVE-2021-42258: BQE BillQuick Web Suite SQL Injection

> Unauthenticated SQL injection in BQE BillQuick Web Suite allows remote code execution and ransomware installation via xp_cmdshell.

- **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:** Yes, since 3 Nov 2021 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Oct 2021
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-69qp-6hh5-mpjp

## What is CVE-2021-42258?

CVE-2021-42258 is a critical SQL injection vulnerability in n/a, published on 22 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BQE BillQuick Web Suite 2018 through 2021 before 22.0.9.1 allows SQL injection for unauthenticated remote code execution, as exploited in the wild in October 2021 for ransomware installation. SQL injection can, for example, use the txtID (aka username) parameter. Successful exploitation can include the ability to execute arbitrary code as MSSQLSERVER$ via xp_cmdshell.

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

## Which versions are affected by CVE-2021-42258?

It affects 1 product.


Products: Bqe Billquick Web Suite.

## How do I fix CVE-2021-42258?

No fix has been published for CVE-2021-42258 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 17 Nov 2021.

## Is CVE-2021-42258 being exploited?

Yes. Attackers have exploited CVE-2021-42258 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Public exploit code:

- BillQuick Web Suite txtID SQLi (metasploit)
- BillQuick Web Suite SQL Injection (nuclei): http/cves/2021/CVE-2021-42258.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-42258 and fix it if it is affected.

What it is: CVE-2021-42258 is a critical SQL injection vulnerability in n/a, published on 22 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2021-42258 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Affected product: n/a. 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-2021-42258/ (Markdown: https://insights.sbomify.com/CVE-2021-42258/index.md)
```

## Sources

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

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