LiveActive security incident?Get immediate response
CVE Record

CVE-2022-37205: 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
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2022-37205 is a high-severity SQL injection issue reported in JFinal CMS 5.1.0. An authenticated attacker could potentially affect data confidentiality, integrity, and availability. The source bundle does not identify a vendor patch, and it does not show confirmed active exploitation.

Executive priority

Prioritize this as a high-risk application security issue if JFinal CMS 5.1.0 is in use. The main business risk is unauthorized database access or modification through authenticated CMS functionality.

Technical view

The CVE describes multiple JFinal CMS interfaces using independent SQL string concatenation without shared filtering, causing CWE-89 SQL injection. CVSS 3.1 is 8.8 with network access, low complexity, low privileges, no user interaction, unchanged scope, and high CIA impact.

Likely exposure

Exposure is most likely where JFinal CMS 5.1.0 is deployed and reachable by users with low-privilege accounts. The structured affected metadata lists vendor/product as n/a, so confirm product and version from asset inventory before scoping.

Exploitation context

The bundle includes public GitHub references for the issue, but KEV is false and no cited source confirms active exploitation. Treat exploitability as plausible because the CVSS vector indicates low complexity after authentication.

Researcher notes

Evidence supports CWE-89 in JFinal CMS 5.1.0, but affected CPE/vendor fields are incomplete and no patch is named. Avoid broad product assumptions. Validate exposure locally and track upstream guidance before declaring remediation complete.

Mitigation direction

  • Identify any JFinal CMS 5.1.0 deployments in production and staging.
  • Check official project or vendor guidance for fixed versions or patches.
  • Limit access to affected CMS interfaces until remediation is confirmed.
  • Review custom code for SQL concatenation and replace it with parameterized queries.
  • Increase monitoring for suspicious authenticated CMS activity.

Validation and detection

  • Confirm installed JFinal CMS versions from asset inventory and application files.
  • Map exposed CMS interfaces reachable by low-privilege authenticated users.
  • Review relevant code paths for SQL string concatenation without filtering.
  • Check application and database logs for unusual authenticated query activity.
  • Document whether a vendor fix or configuration mitigation is available.
Prepared
Confidence
medium
Sources
4

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-37205 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-37205Attack 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
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.