# CVE-2022-47105: Jeecg-boot is vulnerable to SQL injection

> An attacker can exploit a SQL injection flaw in the Jeecg-boot application to read or modify database contents.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Jan 2023
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-6w89-c65w-jx2c

## What is CVE-2022-47105?

CVE-2022-47105 is a critical SQL injection vulnerability in Jeecg Jeecg Boot, published on 19 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jeecg-boot v3.4.4 was discovered to contain a SQL injection vulnerability via the component /sys/dict/queryTableData.

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

## Which versions are affected by CVE-2022-47105?

4 open source packages ship an affected version, including org.jeecgframework.boot:jeecg-boot-base-core and org.jeecgframework.boot:jeecg-module-system. It affects 1 product.


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

Products: Jeecg Jeecg Boot.

## How do I fix CVE-2022-47105?

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

## Is CVE-2022-47105 being exploited?

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

## 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-2022-47105 and fix it if it is affected.

What it is: CVE-2022-47105 is a critical SQL injection vulnerability in Jeecg Jeecg Boot, published on 19 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-47105 exists.

Affected packages and fixed versions:
- org.jeecgframework.boot:jeecg-boot-base-core (Maven): affected all versions up to 3.4.4; no fix listed
- org.jeecgframework.boot:jeecg-boot-base-core (Maven): affected all versions up to 3.4.4; no fix listed
- org.jeecgframework.boot:jeecg-module-system (Maven): affected all versions up to 3.4.4; no fix listed
- org.jeecgframework.boot:jeecg-module-system (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-2022-47105/ (Markdown: https://insights.sbomify.com/CVE-2022-47105/index.md)
```

## Sources

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

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