High

mssql-mcp-core: SQL injection in mssql-mcp write tools via unparameterized table names and WHERE clauses

  • Disclosed: 19.11.2026
  • Updated: 19.11.2026 10:00

Several tools in mssql-mcp-core built T-SQL by string-interpolating caller-supplied identifiers and predicates directly into the statement passed to the node-mssql Request.query() batch API. Only data values were parameterized.

Affected tools and inputs:

  • update_data, delete_data: tableName and the free-form whereClause were interpolated raw.
  • insert_data: tableName and column names (object keys) were interpolated raw.
  • execute_transaction: the same raw tableName/whereClause interpolation per operation.
  • create_table, create_index, drop_table: table/column/index/schema identifiers were interpolated with no or insufficient validation.
  • list_databases (reader tier): the stateFilter argument was interpolated raw into the query, with only a non-enforced inputSchema enum guarding it.

The only check on whereClause was that it was non-empty. Because the row-count and preview queries run before the confirmUpdate/confirmDelete step, a malicious whereClause or tableName executed on the first call, bypassing the preview/confirmation and maxRows safety controls. Request.query() submits a multi-statement T-SQL batch, so a crafted input enabled stacked statements (arbitrary DDL/DML), sub-selects, and (with a privileged login and xp_cmdshell enabled) OS command execution. Because list_databases is a read-only tool, the stateFilter sink makes the reader package injectable as well.

Impact

An actor who can supply tool arguments (a malicious or compromised MCP client, or an LLM agent steered via indirect prompt injection) could read, modify, or drop arbitrary data, bypass the read_data allow/deny validation and the preview/confirmation/maxRows safeguards, and conditionally achieve OS command execution.

Patches

Fixed in @connorbritain/mssql-mcp-core 0.6.0:

  • All identifiers are validated against a strict allowlist and bracket-quoted via a shared helper.
  • The free-form whereClause string parameter is removed (breaking change) and replaced with structured, parameterized filters ({ column, operator, value }) using an operator allowlist. Values are always bound, never interpolated.
  • list_databases validates stateFilter against a fixed allowlist before use.

Upgrade the consumer packages: mssql-mcp-reader 0.5.0, mssql-mcp-writer 0.5.0, mssql-mcp-server 0.6.0 (all depend on core ^0.6.0).

Workarounds

Upgrading is the only complete fix; the list_databases (stateFilter) sink is reachable even under READONLY=true and in the reader package. As defense in depth, run the server under a least-privilege SQL login with xp_cmdshell disabled, and restrict which MCP clients can invoke the tools.

What to do

Upgrading is the only complete fix:

  • Upgrade @connorbritain/mssql-mcp-core to version 0.6.0 or higher.
  • Upgrade consumer packages:
    • mssql-mcp-reader to 0.5.0
    • mssql-mcp-writer to 0.5.0
    • mssql-mcp-server to 0.6.0

As defense in depth, run the server under a least-privilege SQL login with xp_cmdshell disabled, and restrict which MCP clients can invoke the tools.

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
npm package @connorbritain/mssql-mcp-core < 0.6.0 0.6.0
npm package @connorbritain/mssql-mcp-reader < 0.5.0 0.5.0
npm package @connorbritain/mssql-mcp-server < 0.6.0 0.6.0
npm package @connorbritain/mssql-mcp-writer < 0.5.0 0.5.0

References

CVSS score 8.8/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE)
CWE-89
Platform
npm
Package
@connorbritain/mssql-mcp-core, @connorbritain/mssql-mcp-reader, @connorbritain/mssql-mcp-server
Disclosed
19.11.2026
Updated
19.11.2026 10:00

Sources and licenses · Edited or translated by DockRay; source rights and applicable licenses are retained.

OSV / GitHub Advisory Database - GHSA-2m9m-6cr5-9x25 - CC BY 4.0

Vulnerability history: @connorbritain/mssql-mcp-reader

All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.

This is the only known vulnerability of this package.

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.