How severe is CVE-2022-37199?

CVE-2022-37199 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2022-37199?

CVE-2022-37199 affects the following packages: com.jflyfox:jflyfox_jfinal (Maven). Ecosystems affected: Maven.

How do I fix CVE-2022-37199?

The records we use list no patched version of com.jflyfox:jflyfox_jfinal for CVE-2022-37199. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.

How do I detect CVE-2022-37199 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.jflyfox:jflyfox_jfinal, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2022-37199 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2022-37199 actively exploited in the wild?

Yes. There are 1 known exploit references for CVE-2022-37199, including 1 in-the-wild exploitation observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2022-37199?

CVE-2022-37199 has an EPSS (Exploit Prediction Scoring System) score of 0.9%, placing it in the 60th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2022-37199?

CVE-2022-37199 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2022-37199 published, and has it been updated?

CVE-2022-37199 was published on August 23, 2022 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

CVE-2022-37199 — jflyfox_jfinal

CRITICAL

CVE-2022-37199 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in com.jflyfox:jflyfox_jfinal. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. The records list no fixed version yet; check the vendor advisory below and apply the mitigations in the meantime.

SQL injection in jflyfox jfinal

Also known asGHSA-5rf4-f24c-hpvh

Published

Aug 23, 2022

Updated

Oct 28, 2026

Affected

1 pkg

Patched

See advisory

Exploits

1 known

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs60th percentile — riskier than 60% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

☕com.jflyfox:jflyfox_jfinal

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.jflyfox:jflyfox_jfinal`	all versions	No fix

Affected Products

1 product · 1 configurations

Application

jfinal cmsjflyfox

1 version

5.1.0

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

JFinal CMS 5.1.0 is vulnerable to SQL Injection via /jfinal_cms/system/u…

github.comNVDAug 2022

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.jflyfox:jflyfox_jfinal, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
The records we use list no patched version of com.jflyfox:jflyfox_jfinal for CVE-2022-37199. Check the maintainer's advisory, and where your build allows, override or pin the dependency away from the vulnerable range.
Mitigate without a patch
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2022-37199 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

9.8/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Raw vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CWE Classification

CWE-89SQL Injection

Weaponization

No Nuclei template or Metasploit module yet. 1 public proof-of-concept reference is listed on this page.

Timeline

Disclosed

Aug 23, 2022

First exploit

Aug 25, 2022

2 days after disclosure — rapid exploitation

Last updated

Oct 28, 2026

Identifiers

CVE-2022-37199

GHSA-5rf4-f24c-hpvh

References

Advisorygithub.com · CVE 2022 37199.json Advisorynvd.nist.gov · CVE 2022 37199 Reportgithub.com Packagegithub.com · jfinal cms

Related vulnerabilities

Also affects jflyfox_jfinal

This CVE is critical severity; 2 of 5 other CVEs affecting jflyfox_jfinal are rated as high or higher (top: critical).

CVE-2023-30349CVE-2022-36527CVE-2022-37223CVE-2022-29648CVE-2022-30500

Same weakness: CWE-89

This CVE is critical severity; 1 of 3 other CVEs with CWE-89 is rated as high or higher (top: critical).

CVE-2026-44265CVE-2026-33944CVE-2026-115324Browse all CWE-89

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2022-37199 — jflyfox_jfinal

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

Frequently Asked Questions

Is CVE-2022-37199 in your dependencies?