# CVE-2026-124504: erupts erupt ReportService.java ReportService.queryBiData sql injection


- **Severity:** Medium 5.3 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-f9rp-5h65-7c68

## What is CVE-2026-124504?

CVE-2026-124504 is a medium-severity vulnerability in erupts erupt, published on 9 Nov 2026. 

### Official description

A vulnerability was detected in erupts erupt up to 2.3.0. Affected by this issue is the function ReportService.queryBiData of the file ReportService.java. Performing a manipulation of the argument sort results in sql injection. The attack is possible to be carried out remotely. The exploit is now public and may be used. Upgrading to version 2.4.0 can resolve this issue. The patch is named 8d2eaffc79b977c9d11222b9d435a002dceaa062. It is suggested to upgrade the affected component.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-124504?


## How do I fix CVE-2026-124504?

No fix has been published for CVE-2026-124504 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-124504 being exploited?

There is no known exploitation of CVE-2026-124504 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-124504 and fix it if it is affected.

What it is: CVE-2026-124504 is a medium-severity vulnerability in erupts erupt, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124504 in the wild and no public exploit code.

Affected product: erupts erupt. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-124504/ (Markdown: https://insights.sbomify.com/CVE-2026-124504/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-124504
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-124504
- OSV: https://osv.dev/vulnerability/CVE-2026-124504

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-124504/
Summaries are generated and may contain mistakes; the official description above is the record.