# CVE-2022-37199: SQL injection in jflyfox jfinal

> Attackers can execute arbitrary SQL commands via the user list endpoint in JFinal CMS, potentially reading or modifying 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:** 23 Aug 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-5rf4-f24c-hpvh

## What is CVE-2022-37199?

CVE-2022-37199 is a critical SQL injection vulnerability in Jflyfox Jfinal Cms, published on 23 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

JFinal CMS 5.1.0 is vulnerable to SQL Injection via /jfinal_cms/system/user/list.

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

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

2 open source packages ship an affected version, including com.jflyfox:jflyfox_jfinal. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.jflyfox:jflyfox_jfinal` | Maven | All versions to 5.1.0 | None |
| `com.jflyfox:jflyfox_jfinal` | Maven | All versions to 5.1.0 | None |

Products: Jflyfox Jfinal Cms.

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

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

## Is CVE-2022-37199 being exploited?

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

## Other vulnerabilities in Jflyfox Jfinal Cms

- [CVE-2024-53477](https://insights.sbomify.com/CVE-2024-53477/): Deserialization in n/a (critical 9.8)
- [CVE-2023-47503](https://insights.sbomify.com/CVE-2023-47503/): Code injection in n/a (critical 9.8)
- [CVE-2023-30349](https://insights.sbomify.com/CVE-2023-30349/): Remote code execution in JFinal CMS (critical 9.8)
- [CVE-2022-37204](https://insights.sbomify.com/CVE-2022-37204/): SQL injection in n/a (critical 9.8)
- [CVE-2022-37203](https://insights.sbomify.com/CVE-2022-37203/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-37199 and fix it if it is affected.

What it is: CVE-2022-37199 is a critical SQL injection vulnerability in Jflyfox Jfinal Cms, published on 23 Aug 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-37199 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.jflyfox:jflyfox_jfinal (Maven): affected all versions up to 5.1.0; no fix listed
- com.jflyfox:jflyfox_jfinal (Maven): affected all versions up to 5.1.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-2022-37199/ (Markdown: https://insights.sbomify.com/CVE-2022-37199/index.md)
```

## Sources

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

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