# CVE-2023-1454: jeecg-boot qurestSql sql injection

> Remote attackers can exploit SQL injection in JeecgBoot to read or modify database contents via the apiSelectId parameter.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 17 Mar 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-j72f-4hgp-3mwc

## What is CVE-2023-1454?

CVE-2023-1454 is a medium-severity SQL injection vulnerability in Jeecg Jeecg Boot, published on 17 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability classified as critical has been found in jeecg-boot 3.5.0. This affects an unknown part of the file jmreport/qurestSql. The manipulation of the argument apiSelectId leads to sql injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. The associated identifier of this vulnerability is VDB-223299.

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

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

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


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

Products: Jeecg Jeecg Boot.

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

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

## Is CVE-2023-1454 being exploited?

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

Public exploit code:

- jmreport/qurestSql 未授权SQL注入批量扫描poc Jeecg-Boot是一款基于Spring Boot和Jeecg-Boot-Plus的快速开发平台，最新的jeecg-boot 3.5.0 中被爆出多个SQL注入漏洞。 (github_poc): https://github.com/Sweelg/CVE-2023-1454-Jeecg-Boot-qurestSql-SQLvuln
- CVE-2023-1454,Jeecg-Boot 前台SQL注入,CVE-2023-1454批量检测 (github_poc): https://github.com/padbergpete47/CVE-2023-1454
- jeecg-boot unauthorized SQL Injection Vulnerability (CVE-2023-1454) (github_poc): https://github.com/gobysec/CVE-2023-1454
- JeecgBoot SQL（CVE-2023-1454）sqlmap 注入不出来的情况可以使用该脚本 (github_poc): https://github.com/shad0w0sec/CVE-2023-1454-EXP
- CVE-2023-1454 jeecg-boot Unauthorized SQL injection vulnerability (github_poc): https://github.com/P4x1s/CVE-2023-1454-EXP
- jmreport/qurestSql 未授权SQL注入批量扫描poc (github_poc): https://github.com/cjybao/CVE-2023-1454

## Other vulnerabilities in Jeecg Jeecg Boot

- [CVE-2024-40489](https://insights.sbomify.com/CVE-2024-40489/): Code injection in n/a (critical 9.8)
- [CVE-2024-43028](https://insights.sbomify.com/CVE-2024-43028/): Command injection in n/a (critical 9.8)
- [CVE-2024-48307](https://insights.sbomify.com/CVE-2024-48307/): JeecgBoot SQL Injection vulnerability (critical 9.8)
- [CVE-2023-41542](https://insights.sbomify.com/CVE-2023-41542/): Jeecg Boot SQL injection vulnerability (critical 9.8)
- [CVE-2023-41543](https://insights.sbomify.com/CVE-2023-41543/): Jeecg Boot SQL Injection (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2023-1454 is a medium-severity SQL injection vulnerability in Jeecg Jeecg Boot, published on 17 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-1454 exists.

Affected packages and fixed versions:
- org.jeecgframework.boot:jeecg-boot-common (Maven): affected all versions up to 3.5.0; no fix listed
- org.jeecgframework.boot:jeecg-boot-common (Maven): affected all versions up to 3.5.0; 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-1454/ (Markdown: https://insights.sbomify.com/CVE-2023-1454/index.md)
```

## Sources

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

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