Skip to main content
VulnerabilityPublished Updated

CVE-2022-37205: JFinal CMS · SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.5% chance of exploitation in 30 days – higher than 75% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Sep 2022

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
n/a n/aAffected
  • =5.1.0
Fixed in–

AI-suggested

Given the absence of official patches, European organizations should take immediate steps to mitigate the risk. First, conduct a thorough audit to identify all instances of JFinal CMS 5.1.0 in their environment. Restrict access to the CMS administration interfaces to trusted IP addresses and enforce strong authentication mechanisms. Implement Web Application Firewalls (WAFs) with custom rules to detect and block SQL Injection patterns targeting JFinal CMS. Review and sanitize all user inputs at the application level, applying parameterized queries or prepared statements where possible. If feasible, isolate the CMS environment to limit lateral movement in case of compromise. Monitor logs for suspicious database queries or unusual access patterns. Engage with the vendor or community to obtain updates or patches and plan for an upgrade once available. Additionally, consider deploying database activity monitoring tools to detect and respond to anomalous SQL commands in real time.

Description

JFinal CMS 5.1.0 is affected by: SQL Injection. These interfaces do not use the same component, nor do they have filters, but each uses its own SQL concatenation method, resulting in SQL injection.

References

Community reviews

Loading reviews…