# CVE-2023-24789: jeecg-boot contains SQL Injection vulnerability

> An authenticated SQL injection in JeecgBoot's report component allows attackers to read or modify database contents.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Mar 2023
- **Updated:** 5 Mar 2025
- **Also known as:** GHSA-qxpm-5ghc-6gc2

## What is CVE-2023-24789?

CVE-2023-24789 is a high-severity SQL injection vulnerability in n/a, published on 6 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

jeecg-boot v3.4.4 was discovered to contain an authenticated SQL injection vulnerability via the building block report component.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2023-24789?

2 open source packages ship an affected version, including org.jeecgframework.boot:jeecg-boot-parent. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.jeecgframework.boot:jeecg-boot-parent` | Maven | All versions to 3.4.4 | None |
| `org.jeecgframework.boot:jeecg-boot-parent` | Maven | All versions to 3.4.4 | None |

Products: Jeecg Jeecg.

## How do I fix CVE-2023-24789?

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

## Is CVE-2023-24789 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24789 exists.

## Other vulnerabilities in n/a

- [CVE-2023-49442](https://insights.sbomify.com/CVE-2023-49442/): Deserialization in n/a (critical 9.8)
- [CVE-2021-37304](https://insights.sbomify.com/CVE-2021-37304/): Insecure Permissions issue in jeecg-boot (high 7.5)
- [CVE-2021-37305](https://insights.sbomify.com/CVE-2021-37305/): Insecure Permissions issue in jeecg-boot (high 7.5)
- [CVE-2021-37306](https://insights.sbomify.com/CVE-2021-37306/): Insecure Permissions issue in jeecg-boot (high 7.5)
- [CVE-2020-20948](https://insights.sbomify.com/CVE-2020-20948/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-24789 and fix it if it is affected.

What it is: CVE-2023-24789 is a high-severity SQL injection vulnerability in n/a, published on 6 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-24789 exists.

Affected packages and fixed versions:
- org.jeecgframework.boot:jeecg-boot-parent (Maven): affected all versions up to 3.4.4; no fix listed
- org.jeecgframework.boot:jeecg-boot-parent (Maven): affected all versions up to 3.4.4; no fix listed

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-2023-24789/ (Markdown: https://insights.sbomify.com/CVE-2023-24789/index.md)
```

## Sources

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

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