Skip to main content
HighCodeOWASP A03:2021CWE-89

How to fix: Sequelize.literal with user input

Sequelize.literal(userInput) or Sequelize.fn('CONCAT', userInput, 'x') interpolates raw SQL. When the literal contains user data, the resulting WHERE clause is vulnerable to SQL injection.

Why it matters

SQL injection via Sequelize.literal breaks parameterized query boundaries and can exfiltrate the entire database.

The `code-sqli-sequelize-literal` check verifies that the server does not expose the `sqli-sequelize-literal` 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

  1. 1Use Sequelize replacements: { replacements: [userInput] } instead of literal().
  2. 2Allowlist column or operator names before passing to literal().
  3. 3Wrap identifiers with Sequelize.literal only when names are static.

Code examples

Avoid Sequelize.literal with user input

TypeScript
// BAD: literal() bypasses escaping
User.findAll({ where: Sequelize.literal(`name = '${name}'`) });

// GOOD: use Sequelize where clauses
User.findAll({ where: { name: name } });
// Or with Op:
import { Op } from "sequelize";
User.findAll({ where: { name: { [Op.eq]: name } } });

References

Detected automatically by VulnRadar. The check id is code-sqli-sequelize-literal, stable across every scan so you can filter or diff on it.

See every code check

Questions

How severe is Sequelize.literal with user input?
VulnRadar rates this high 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-sequelize-literal, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Sequelize.literal with user input 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 sequelize.literal with user input

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: Sequelize.literal with user input | VulnRadar