dbcve.org
InjectionWeakness · CWE-74

CVE-2026-5322

HIGH · 7.3 CVSS v3.1 Published 2026-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A vulnerability has been found in AlejandroArciniegas mcp-data-vis bc597e391f184d2187062fd567599a3cb72adf51/de5a51525a69822290eaee569a1ab447b490746d. This affects the function Request of the file src/servers/database/server.js of the component MCP Handler. The manipulation leads to sql injection. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. This product uses a rolling release model to deliver continuous updates. As a result, specific version information for affected or updated releases is not available. The vendor was contacted early about this disclosure but did not respond in any way.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

SQL injection vulnerability in the MCP Handler's Request function within src/servers/database/server.js, allowing remote attackers to inject malicious SQL queries through unsanitized input.

MitigationReplace dynamic SQL queries with parameterized queries/prepared statements and implement proper input validation on all user-supplied data before database execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the affected file
    Search your installation for the file src/servers/database/server.js. Use 'find / -path "*/src/servers/database/server.js" 2>/dev/null' on Linux or similar file search on Windows.
    Affected if The file exists in your environment, indicating you have the MCP database server component installed.
  2. Identify the product version
    Determine the version of the MCP server or application that includes the src/servers/database/server.js file. Check package.json, README, or run 'npm list' if this is a Node.js application.
    Affected if Your installed version falls within the affected version range for this CVE.
  3. Verify MCP database server is enabled
    Check your application configuration files (e.g., config.json, config.yaml, .env) for any settings that enable or load the MCP database server module.
    Affected if The MCP database server component is enabled and loaded in your running configuration.
  4. Check if Request function handles external input
    Review the src/servers/database/server.js file and locate the 'Request' function within the MCP Handler. Determine if this function processes input from external sources (HTTP requests, API calls, user-provided parameters).
    Affected if The Request function processes external/user-supplied input without apparent sanitization.
  5. Inspect database query execution
    Examine the code paths within the Request function that execute SQL queries. Look for string concatenation or template literals used to build SQL queries with user input.
    Affected if SQL queries are constructed using dynamic string concatenation with unsanitized user input.

You are affected if the vulnerable file exists, your product version is within the affected range, the MCP database server is enabled, and the Request function uses unsanitized user input in SQL query execution.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace dynamic SQL queries with parameterized queries/prepared statements and implement proper input validation on all user-supplied data before database execution.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-5322 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-5322 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data