Skip to main content
CriticalCodeOWASP A03:2021CWE-89

How to fix: SQL injection pattern in source

String concatenation or template literals used to build SQL queries with what appears to be user-controlled input.

Why it matters

SQL injection allows an attacker to read arbitrary data from the database, bypass authentication, modify or delete records, and in some configurations execute OS-level commands, a complete database compromise.

Directly concatenating user input into SQL queries allows injection of arbitrary SQL syntax. Always use parameterized queries or prepared statements.

How to fix it

  1. 1Replace string concatenation with parameterized queries ($1, $2 placeholders)
  2. 2Use an ORM (Drizzle, Prisma, Sequelize) with its query builders
  3. 3Apply a Web Application Firewall (WAF) as a defense-in-depth layer

Code examples

Use parameterized queries for all DB operations

TypeScript
// BAD: string interpolation into SQL
const q = `SELECT * FROM users WHERE id = ${id}`;

// GOOD: parameterized query
const result = await pool.query(
  "SELECT * FROM users WHERE id = $1 AND active = $2",
  [id, true]
);

// With an ORM:
import { eq } from "drizzle-orm";
const user = await db.select().from(users).where(eq(users.id, id));

References

Detected automatically by VulnRadar. The check id is sql-injection-patterns, stable across every scan so you can filter or diff on it.

See every code check

Questions

How severe is SQL injection pattern in source?
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 sql-injection-patterns, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does SQL injection pattern in source 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.

Propose a checkHow a check is built

Scan your own site for sql injection pattern in source

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: SQL injection pattern in source | VulnRadar