Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries in ORM
|
| Impact | The CVSS 3.1 score of 6.3 (Medium) with vector AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L indicates the vulnerability requires network access and valid authentication (PR:L) but has low attack complexity. The real-world risk is elevated beyond the base CVSS score due to several aggravating factors: a publicly available exploit reduces exploitation barriers significantly, the vendor's non-response to early disclosure suggests no patch timeline, and SQL injection's well-understood attack patterns make automation trivial. However, the requirement for authenticated access (PR:L) limits the attack surface compared to unauthenticated SQL injection vulnerabilities. Organizations should treat this as a high-priority issue for any production Erupt deployment with untrusted user access or where internal users have elevated privileges, as the confidentiality, integrity, and availability impact is measurable across all three dimensions. |
| Exploit ScenarioDerived | An authenticated user with access to the Erupts Erupt application submits a specially crafted query through the MCP Tool Interface that targets the EruptDataQuery function. By injecting SQL metacharacters and Hibernate-specific syntax into the query parameters, the attacker bypasses input validation and executes arbitrary SQL against the backend database without explicit authorization. For example, a malicious query could extract sensitive data from tables beyond the attacker's normal access level, modify or delete records, or potentially escalate privileges depending on database user permissions. Since a public exploit is available, an attacker with basic SQL injection knowledge can easily adapt existing code to their target environment. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 23, 2026
SQL injection in Erupt's MCP Tool Interface allows authenticated attackers to manipulate database queries through the EruptDataQuery component, potentially exposing or modifying sensitive data. The vulnerability affects Java-based Erupt deployments version 1.13.3 and has public exploit code available. No patch is currently available from the vendor, who has not responded to disclosure efforts.
Earlier versions of this analysis (1)
A SQL injection vulnerability exists in Erupts Erupt bis version 1.13.3 within the EruptDataQuery component of the MCP Tool Interface, allowing authenticated attackers to execute arbitrary SQL queries through Hibernate ORM. The vulnerability affects the cpe:2.3:a:erupts:erupt product line and has a publicly available exploit with no vendor response despite early disclosure, making it an active risk for organizations running vulnerable versions.
RemediationAI
Immediate action requires upgrading Erupts Erupt to a patched version beyond 1.13.3 if available from the vendor, though note that the vendor has not responded to early disclosure efforts, which may complicate obtaining official patches. As an interim mitigation, restrict network access to the MCP Tool Interface to only trusted internal networks and implement strict authentication controls to limit PR:L exposure to authorized users only. Apply database-level access controls to limit the Erupt application's database user permissions to only necessary tables and operations, reducing the impact scope of successful SQL injection exploitation. Additionally, implement Web Application Firewall (WAF) rules to detect and block common SQL injection patterns in requests to the EruptDataQuery endpoint, monitor database query logs for anomalous activity, and consider disabling the MCP Tool Interface entirely if it is not actively required for operations. Reference the VulDB entries at https://vuldb.com/?submit.775593 and the published exploit details at https://fx4tqqfvdw4.feishu.cn/docx/EunDdwORZoG3uzxpLykcj24mncJ?from=from_copylink for technical analysis to inform filtering rules.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in the EruptDataQuery.java file within the erupt-ai module, which handles data query operations through the MCP (Model Context Protocol) Tool Interface. The root cause is classified under CWE-564 (Unsafe Name Mapping), indicating improper handling of user-supplied input that gets passed directly to Hibernate ORM queries without adequate sanitization or parameterization. Erupts Erupt is a low-code/no-code rapid development framework built on Java, and the MCP Tool Interface is designed to bridge external tools with the Erupt data layer. When user input from MCP tools is passed to the EruptDataQuery function, it bypasses proper input validation and becomes part of Hibernate query construction, enabling SQL injection attacks at the database level.
Know when Erupt gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
5DescriptionCVE.org
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.
Executive ViewAI
Organizations using A flaw should be aware of moderate risk from CVE-2026-4593 rated CVSS 6.3. Exploitation could compromise the security of affected deployments. Proof-of-concept code is publicly available. Organizations should apply vendor updates when available and monitor for exploitation.
Apply vendor patch. If patching is delayed: restrict network access and enable monitoring.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
Affected Products (CPE)CVE.org
Related Vulnerabilities in erupts erupt Data Query Flaws
View all 2Authenticated HQL injection in Erupt through version 2.3.0 lets a user who already holds query permission on an entity w
An arbitrary file upload vulnerability in the component /upload/GoodsCategory/image of erupt v1.12.19 allows attackers t
EUVD-2026-14473
GHSA-473j-28g3-gv2f
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB