mssql-mcp-core write tools have SQL injection vulnerabilities because table names and WHERE clauses are not parameterized
mssql-mcp-core: SQL injection in mssql-mcp write tools via unparameterized table names and WHERE clauses
mssql-mcp-core released a security advisory (CVE-2026-63129): its MSSQL MCP tool directly concatenates table names, column names and whereClause into T-SQL without parameterization, resulting in SQL injection; versions 0.5.0 and earlier are affected, and it has been fixed in 0.6.0. Because the preview query executes before the confirmation step, malicious input can be triggered on the first call, bypassing the preview/confirmation and maxRows protections; queries are submitted as multi-statement batches, allowing arbitrary DDL/DML, and when logged in with privileges and xp_cmdshell is enabled, operating system commands may also be executed. A malicious or compromised MCP client capable of supplying tool parameters, or an LLM agent guided by indirect prompt injection, can use this to read, modify or delete arbitrary data.
The advisory states that an LLM agent guided by indirect prompt injection can exploit this injection; teams using this MCP server can use this to check dependency versions and upgrade.