CVE-2026-4594
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 · uneditedA 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.
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 · moderate confidenceSQL injection vulnerability in the geneEruptHqlOrderBy function of EruptJpaUtils.java. The sort.field parameter is not sanitized before being incorporated into Hibernate Query Language (HQL) ORDER BY clauses, allowing remote attackers to inject arbitrary SQL code via crafted input.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Erupt framework installationSearch for EruptJpaUtils.java in your codebase or check Maven/Gradle dependencies for the erupt framework artifact (typically com.erupt or erupt:erupt-*)Affected if The Erupt framework is present in your environment
-
Determine Erupt versionCheck your build configuration (pom.xml, build.gradle) or the jar manifest for the exact Erupt version numberAffected if You cannot determine the version or are running a version that includes the geneEruptHqlOrderBy function
-
Check if sorting functionality is exposedReview your application endpoints to determine if any API accepts a sort.field or sortField parameter, typically through REST controllers or data table components that use Erupt's sorting featuresAffected if Sorting parameters are accepted by your exposed endpoints
-
Verify geneEruptHqlOrderBy is in useSearch your deployed EruptJpaUtils.java or compiled classes for the geneEruptHqlOrderBy method and trace if it handles user-supplied sort.field input without sanitizationAffected if The vulnerable function processes unsanitized sort.field input from requests
-
Review input validation on sort parametersExamine any filters, interceptors, or validation logic that process the sort.field parameter before it reaches the HQL query builder in geneEruptHqlOrderByAffected if No input validation or allowlist validation exists for the sort.field parameter
You are affected if you are running the Erupt framework with the vulnerable geneEruptHqlOrderBy function and the sorting feature that accepts sort.field input is enabled and reachable from your application endpoints.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strict allowlist validation or parameterized query binding for sort.field input in the geneEruptHqlOrderBy function. Until official patch is released, restrict or disable the sorting functionality exposed through this endpoint.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-4594 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4594 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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