LiveActive security incident?Get immediate response
CVE Record

CVE-2022-37209: JFinal CMS 5.1.0 is affected by: SQL Injection.

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.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

JFinal CMS 5.1.0 has a high-severity SQL injection flaw. An authenticated attacker could potentially tamper with database queries, exposing, changing, or disrupting data. The public record does not name a fixed version or official mitigation.

Executive priority

Prioritize within the normal high-severity remediation window, faster for internet-facing CMS deployments or systems holding sensitive data. Business risk is data exposure and database manipulation by authenticated attackers.

Technical view

CVE-2022-37209 is CWE-89 SQL injection in JFinal CMS 5.1.0. The CVSS 3.1 vector is 8.8 high: network reachable, low complexity, low privileges, no user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely where JFinal CMS 5.1.0 is deployed, especially internet-accessible CMS interfaces requiring low-privileged authentication. The CVE metadata does not provide vendor CPEs or a broader affected-version range.

Exploitation context

The CVE references public GitHub materials, but the provided sources do not establish active exploitation. It is not listed as CISA KEV in the source bundle. Treat exploitability as plausible because CVSS indicates low complexity and network access.

Researcher notes

Evidence is limited to the CVE description, CVSS vector, CWE-89 classification, and referenced GitHub pages. The source bundle does not name patched versions, affected CPEs, specific interfaces, or confirmed exploitation.

Mitigation direction

  • Identify any JFinal CMS 5.1.0 deployments in production and staging.
  • Check official project or vendor guidance for a fixed version or patch.
  • Restrict access to CMS interfaces to trusted networks or VPN users.
  • Review maintained forks for SQL string concatenation in affected interfaces.
  • Increase monitoring for database errors and suspicious authenticated CMS requests.

Validation and detection

  • Confirm application name and version from asset inventory or deployment artifacts.
  • Map externally reachable JFinal CMS routes and authentication boundaries.
  • Review web and database logs for unusual query errors or tampering indicators.
  • Use code review or SAST to find SQL concatenation in CMS interfaces.
  • Verify any vendor patch or upgrade in staging before production rollout.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-37209 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

8.8High
CVSS 3.1 vector shape for CVE-2022-37209Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE-89

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.