dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-4593

MEDIUM · 6.3 CVSS v3.1 Published 2026-03-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 flaw has been found in erupts erupt bis 1.13.3. Affected by this vulnerability is the function EruptDataQuery of the file erupt-ai/src/main/java/xyz/erupt/ai/call/impl/EruptDataQuery.java of the component MCP Tool Interface. This manipulation causes sql injection hibernate. It is possible to initiate the attack remotely. The exploit has been published and may be used. 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 EruptDataQuery function of the erupt-ai module (versions up to 1.13.3). The function fails to properly sanitize or parameterize inputs when constructing Hibernate queries, allowing attackers to inject arbitrary SQL commands through the MCP Tool Interface.

MitigationUpgrade to a patched version if available; otherwise, implement proper parameter binding for all Hibernate queries in the affected function and validate/sanitize all user inputs before query construction.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify if erupt-ai module is present
    Search the project dependencies (Maven pom.xml, Gradle build.gradle, or package.json) for 'erupt-ai' or search for files containing 'erupt-ai' in the codebase
    Affected if The erupt-ai module is present in the project dependencies
  2. Check installed erupt-ai version
    Locate the erupt-ai library in the project's dependency management system or build artifacts and determine the exact version number (e.g., from pom.xml, build.gradle, or the JAR file name)
    Affected if The installed version is 1.13.3 or any earlier version up to and including 1.13.3
  3. Verify EruptDataQuery function is in use
    Search the codebase for any Java/Kotlin files that import or reference 'EruptDataQuery' from the erupt-ai module, or for any code calling this function
    Affected if Code explicitly invokes or references the EruptDataQuery function from erupt-ai
  4. Confirm Hibernate queries are constructed without parameterization
    Examine the source code of the EruptDataQuery implementation (or any wrapper around it) to verify that user inputs are directly concatenated into Hibernate Query Language (HQL) strings rather than using parameterized queries or prepared statements
    Affected if User-provided input values are concatenated directly into query strings without using parameter binding or input sanitization
  5. Determine if MCP Tool Interface is exposed
    Review application configuration and network exposure settings to check whether the MCP (Model Context Protocol) Tool Interface endpoint is enabled and accessible to external inputs
    Affected if The MCP Tool Interface is enabled and accessible, allowing external data to reach the EruptDataQuery function

You are affected if the erupt-ai module version 1.13.3 or lower is installed, the EruptDataQuery function is in use, and the MCP Tool Interface can deliver untrusted input to queries that are not using parameterized binding.

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

Upgrade to a patched version if available; otherwise, implement proper parameter binding for all Hibernate queries in the affected function and validate/sanitize all user inputs before query construction.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4593 — 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-4593 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