How exploitable is this vulnerability in practice?

Exploitability depends on whether an attacker can control JSON object keys that your application passes into Sequelize's JSON/JSONB querying APIs. If keys are derived directly or indirectly from request data without restriction, exploitation is typically straightforward.

Does an attacker need authenticated access to exploit this issue?

Not necessarily. If unauthenticated endpoints accept JSON input and feed it into affected Sequelize queries, an anonymous attacker may exploit the bug. In many applications, however, the vulnerable paths are behind authenticated APIs, limiting exploitation to authenticated users with access to those endpoints.

What is the safest general fix pattern for this type of bug?

The safest pattern is to avoid deriving SQL syntax elements—such as type names, operators, or identifiers—from user-controlled input. Instead, map any dynamic behavior to a fixed allowlist of supported types and operators, and use ORM or parameterized query APIs that prevent raw string injection.

Severity:

HIGH RISK

(7.5)

SQL Injection via Unescaped JSON Cast Type (CWE-89) in Sequelize JSON/JSONB Where Clauses

CVE-2026-30951

Published:

Mar 10, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Data Exfiltration and Query Manipulation

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Vulnerability Type

Category:

SQL Injection

CWE:

CWE-89

Impact:

Data Exfiltration and Query Manipulation

Severity:

HIGH RISK

(7.5)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

SQL Injection via Unescaped JSON Cast Type (CWE-89) in Sequelize JSON/JSONB Where Clauses

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal