Skip to main content

Erupt CVE-2026-4594

| EUVDEUVD-2026-14475 MEDIUM
SQL Injection: Hibernate (CWE-564)
2026-03-23 VulDB GHSA-8fx2-x558-87xq
5.5
CVSS 4.0 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Send HTTP request with malicious sort.field parameter
  2. Exploit
    Inject SQL payload into geneEruptHqlOrderBy function
  3. Execution
    Hibernate executes crafted SQL query
  4. Impact
    Extract or modify database records

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries in ORM
Exploitation Conditions

Remote unauthenticated attacker can exploit erupts erupt versions up to 1.13.3 by manipulating the sort.field parameter in the geneEruptHqlOrderBy function to inject SQL via Hibernate. No special configuration or victim interaction required.

Impact

The real-world risk is HIGH and this should be prioritized for remediation. The CVSS v3.1 score of 7.3 reflects critical risk factors: network-based attack vector (AV:N), low attack complexity (AC:L), and no authentication required (PR:N). Most concerning is the public availability of a working exploit (E:P) as evidenced by the Feishu document reference containing proof-of-concept code, transforming this from theoretical to immediately exploitable. The CVSS vector indicates impact across all three security pillars (C:L/I:L/A:L), meaning attackers can read, modify, and disrupt data. The vendor's non-responsiveness (RL:X indicating no official remedy) compounds the risk, leaving users without vendor-supported patches. This vulnerability is automatable given the low complexity and remote exploitation vector, making it attractive for both targeted attacks and mass scanning campaigns. Organizations running affected versions should treat this as an active threat requiring immediate action.

Exploit ScenarioDerived

An unauthenticated remote attacker crafts a malicious HTTP request to the erupt application, targeting an endpoint that uses the vulnerable sorting functionality. The attacker manipulates the sort.field parameter with HQL injection payloads such as '(CASE WHEN (SELECT COUNT(*) FROM User)>0 THEN id ELSE name END)' to exfiltrate data or '1=1; DELETE FROM SensitiveTable--' to manipulate database records. Since a public proof-of-concept is available via the Feishu document reference, attackers can readily adapt the disclosed exploit code to target vulnerable installations, requiring minimal technical sophistication due to the low attack complexity.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 23, 2026

SQL injection in Erupt up to version 1.13.3 allows unauthenticated remote attackers to execute arbitrary SQL queries through the sort.field parameter in the HQL query builder. Public exploit code exists for this vulnerability, and no patch is currently available. Affected Java applications using vulnerable versions of Erupt are at risk of data exfiltration and manipulation.

Earlier versions of this analysis (1)
v1 Mar 23, 2026 - 18:00 CVSS 7.3

A SQL injection vulnerability exists in the erupts erupt framework through version 1.13.3, affecting the geneEruptHqlOrderBy function in the EruptJpaUtils.java file. The vulnerability allows remote attackers without authentication to inject malicious SQL through the sort.field parameter, potentially compromising data confidentiality, integrity, and availability. A public proof-of-concept exploit has been disclosed and is available, significantly increasing the risk of active exploitation.

RemediationAI

Upgrade to erupts erupt version 1.13.4 or later if the vendor has released a patched version, though no official patch has been confirmed as the vendor did not respond to disclosure attempts. In the absence of vendor patches, immediately implement input validation and sanitization on all user-controllable sort parameters before they reach the geneEruptHqlOrderBy function. Use parameterized queries or Hibernate Criteria API instead of dynamic HQL string concatenation for ORDER BY clauses. Apply a whitelist-based validation approach that only allows predefined, safe column names for sorting operations. As an additional defense layer, restrict network access to the application to trusted IP ranges and implement web application firewall (WAF) rules to detect and block SQL injection patterns. Monitor application logs for suspicious sorting parameter values that contain SQL keywords or special characters. Given the vendor's lack of response, consider migrating to an actively maintained alternative framework if this component is critical to your infrastructure.

Affected VersionsENISA

erupt 1.13.0
erupt 1.13.2
erupt 1.13.1
erupt 1.13.3

Affected Packages

euvd erupt no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

This vulnerability affects the erupts erupt framework (CPE: cpe:2.3:a:erupts:erupt), specifically the JPA (Java Persistence API) data layer component. The flaw is classified as CWE-564 (SQL Injection: Hibernate), indicating improper input validation when constructing Hibernate Query Language (HQL) statements. The geneEruptHqlOrderBy function in EruptJpaUtils.java fails to properly sanitize the sort.field parameter before incorporating it into HQL ORDER BY clauses. Unlike traditional SQL injection, HQL injection targets the object-relational mapping layer, allowing attackers to manipulate queries executed against the underlying database through Hibernate's query translation mechanism. This type of injection can bypass typical SQL injection defenses if developers assume ORM frameworks inherently prevent injection attacks.

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

NVD PRIMARY 5.5 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/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

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

5
CVSS changed
Apr 29, 2026 - 01:11 NVD
6.9 (MEDIUM) 5.5 (MEDIUM)
Severity Changed
Apr 24, 2026 - 16:37 NVD
HIGH MEDIUM
CVSS changed
Apr 24, 2026 - 16:37 NVD
7.3 (HIGH) 6.9 (MEDIUM)
PoC Detected
Mar 24, 2026 - 15:54 vuln.today
Public exploit code
CVE Published
Mar 23, 2026 - 17:41 nvd
HIGH 7.3

DescriptionCVE.org

A vulnerability has been found in erupts erupt up to 1.13.3. Affected by this issue is the function geneEruptHqlOrderBy of the file erupt-data/erupt-jpa/src/main/java/xyz/erupt/jpa/dao/EruptJpaUtils.java. Such manipulation of the argument sort.field leads to sql injection hibernate. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Executive ViewAI

Why It Matters

A critical SQL injection vulnerability in the Erupt framework (versions through 1.13.3) allows unauthenticated attackers to compromise sensitive data and system integrity. With a public exploit actively circulating, any organization using this framework faces immediate risk of data breach, unauthorized access, and potential system takeover.

Business Impact: Severe
Compensating Controls

Implement Web Application Firewall (WAF) rules to block requests with suspicious sort.field parameters; disable the affected sort functionality if operationally feasible; restrict network access to Erupt applications via IP whitelisting or VPN; implement database activity monitoring and SQL injection detection signatures; apply principle of least privilege to database service accounts.

Threat Intelligence Overview

EPSS Score
0.0%
Top 92% exploitable
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Out-of-Cycle
Exploitation
Poc
System Exposure· derived
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Partial

Priority Score

48
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.

Related Vulnerabilities in erupts erupt Data Query Flaws

View all 2

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy