How to fix: SQL via template literal interpolation
Tag-less template literals like pool.query(`SELECT * FROM t WHERE id = ${id}`) interpolate user input directly into SQL text. Tagged sql`` libraries are safe; bare backticks are not.
Why it matters
Template-literal SQL injection exposes all rows the caller can see and can pivot to RCE on the database host.
The `code-sqli-template-literal-query` check verifies that the server does not expose the `sqli-template-literal-query` 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
- 1Switch to a tagged template SQL helper (sql`...`) that auto-parameterizes.
- 2Or use placeholders: pool.query('SELECT * FROM t WHERE id = $1', [id]).
- 3Add a lint rule banning untagged template SQL.
Code examples
Never use template literals for SQL
// BAD
const q = `SELECT * FROM orders WHERE user_id = ${userId}`;
// GOOD: parameter placeholder
const q = "SELECT * FROM orders WHERE user_id = $1";
const result = await pool.query(q, [userId]);References
Detected automatically by VulnRadar. The check id is code-sqli-template-literal-query, 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 SQL via template literal interpolation?
- 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-template-literal-query, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does SQL via template literal interpolation 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.