How to fix: Raw query string concatenation
db.query("SELECT * FROM users WHERE id = '" + userId + "'") or knex.raw(`SELECT * FROM x WHERE id = ${userId}`) build a SQL string from user input, enabling classic SQL injection.
Why it matters
Classic SQL injection: data exfiltration, authentication bypass, and potentially full RCE on the database server.
The `code-sqli-raw-query-string` check verifies that the server does not expose the `sqli-raw-query-string` weakness in the code category. The detection runs against the response headers, body, or auxiliary probes (DNS, TLS, async fetch) as appropriate.
How to fix it
- 1Use parameterized queries or prepared statements with placeholders.
- 2Replace knex.raw with knex('table').where({ id: userId }).
- 3Run a query allowlist review for every knex.raw / sequelize.literal / db.query call site.
Code examples
Use parameterized queries
import pool from "./db";
// BAD: string concatenation, SQL injection
const result = await pool.query(`SELECT * FROM users WHERE email = '${email}'`);
// GOOD: parameterized query
const result = await pool.query(
"SELECT * FROM users WHERE email = $1",
[email]
);References
Detected automatically by VulnRadar. The check id is code-sqli-raw-query-string, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is Raw query string concatenation?
- VulnRadar rates this critical severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id code-sqli-raw-query-string, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Raw query string concatenation map to?
- It maps to CWE-89. In the OWASP Top 10 it falls under A03:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.