Skip to main content
VulnerabilityPublished Updated

CVE-2022-37204: Final CMS · SQL Injection

Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 12:54 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.4% chance of exploitation in 30 days – higher than 73% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/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
GitHubagainstthelight/jfinal_cmspkg:github/againstthelight/jfinal_cmsOther threatsAffected
  • =5.1.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

  1. Immediate upgrade: Organizations should verify their Final CMS version and upgrade to a patched version if available.
  2. Input validation and sanitization: Implement strict input validation and parameterized queries or prepared statements in the CMS codebase to prevent injection.
  3. Web Application Firewall (WAF): Deploy and configure a WAF with rules to detect and block SQL injection attempts targeting Final CMS.
  4. Network segmentation: Isolate CMS servers from critical backend systems and databases to limit potential damage.
  5. Monitoring and logging: Enable detailed logging of database queries and web requests to detect suspicious activity indicative of exploitation attempts.
  6. Access controls: Restrict database user privileges to the minimum necessary to reduce impact if exploited.
  7. Incident response readiness: Prepare to respond quickly to any detected exploitation, including isolating affected systems and conducting forensic analysis.

Description

Final CMS 5.1.0 is vulnerable to SQL Injection.

References

Community reviews

Loading reviews…