Security readout for executives and security teams
Plain-English summary
Final CMS 5.1.0 is reported vulnerable to SQL injection. An unauthenticated attacker could potentially affect confidentiality, integrity, and availability of the underlying application data. The public record is sparse, so urgency comes from the critical CVSS rating and vulnerability class, not from confirmed exploitation.
Executive priority
Handle as urgent if Final CMS 5.1.0 is present, especially on public systems. The risk is potentially business-critical data compromise or service disruption, but current sources do not prove active exploitation or provide a named patch.
Technical view
CVE-2022-37204 is classified as CWE-89 SQL injection with CVSS 3.1 score 9.8: network-accessible, low complexity, no privileges, no user interaction, unchanged scope, and high CIA impact. The bundle names Final CMS 5.1.0, but affected vendor/product metadata and CPEs are not populated.
Likely exposure
Organizations running Final CMS 5.1.0 are the stated exposure group, especially if the CMS is internet-facing. Because the CVE affected fields list n/a and no CPEs, vulnerability managers may need application inventory, code ownership, or deployment records rather than relying on CPE matching.
Exploitation context
The bundle includes public GitHub references, but does not include CISA KEV status or another cited source confirming active exploitation. Treat this as a critical exposure because unauthenticated network SQL injection can be severe, while being clear that active exploitation is not established here.
Researcher notes
The source record is minimal. It identifies SQL injection in Final CMS 5.1.0 and provides GitHub references, but lacks structured affected CPEs, vendor metadata, patch status, and confirmed exploitation evidence. Avoid expanding scope beyond the named version without additional evidence.
Mitigation direction
- Inventory systems for Final CMS 5.1.0 and prioritize internet-facing instances.
- Check Final CMS maintainer or deployment owner guidance for fixed versions or supported upgrade paths.
- Restrict public access to affected CMS instances while remediation is being determined.
- Review database account privileges used by the CMS and reduce excessive permissions where feasible.
- Increase monitoring for SQL errors, abnormal queries, and suspicious CMS request patterns.
Validation and detection
- Confirm whether any deployed application is Final CMS 5.1.0.
- Do not rely solely on CPE matching; the CVE record lacks populated CPE data.
- Review public exposure through asset inventory, DNS, reverse proxies, and hosting records.
- Check application and database logs for unusual errors or unauthorized data access indicators.
- Document whether vendor guidance, upgrade evidence, or compensating controls exist for each instance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupDatabase 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 lookupCVE-2022-37204 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/AgainstTheLight/someEXP_of_jfinal_cms/blob/main/jfinal_cms/sql7.mdCVE reference · x_refsource_MISC
- https://github.com/AgainstTheLight/CVE-2022-37204/blob/main/README.mdCVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.