CVE-2026-4594
SQL Injection in EruptJpaUtils.java Enables Remote Exploitation
Publication date: 2026-03-23
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| erupt | erupt | to 1.13.3 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-564 | Using Hibernate to execute a dynamic SQL statement built with user-controlled input can allow an attacker to modify the statement's meaning or to execute arbitrary SQL commands. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
I don't know
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
Can you explain this vulnerability to me?
This vulnerability exists in the erupt software up to version 1.13.3, specifically in the function geneEruptHqlOrderBy within the file erupt-data/erupt-jpa/src/main/java/xyz/erupt/jpa/dao/EruptJpaUtils.java.
The issue arises from improper handling of the argument sort.field, which can be manipulated to perform SQL injection attacks through Hibernate.
An attacker can exploit this vulnerability remotely, and the exploit has already been publicly disclosed.
How can this vulnerability impact me? :
This vulnerability allows an attacker to perform SQL injection attacks remotely by manipulating the sort.field argument.
Such an attack can lead to unauthorized access, data leakage, data modification, or disruption of the affected system's database operations.
Because the exploit is publicly known, systems running vulnerable versions are at increased risk of compromise.