CVE-2022-37773: An authenticated SQL Injection vulnerability in the statistics page (/statistics/retrieve) of Maarch RM 2.8...
An authenticated SQL Injection vulnerability in the statistics page (/statistics/retrieve) of Maarch RM 2.8, via the filter parameter, allows the complete disclosure of all databases.
Security readout for executives and security teams
Plain-English summary
CVE-2022-37773 is an authenticated SQL injection in Maarch RM 2.8. A logged-in attacker could use the statistics retrieval function to expose database contents. The main business risk is confidentiality loss, not system takeover, based on the published CVSS vector.
Executive priority
Treat as a moderate-priority confidentiality issue. Prioritize if Maarch RM stores sensitive records or allows broad authenticated user access.
Technical view
The CVE describes CWE-89 SQL injection in Maarch RM 2.8 at /statistics/retrieve through the filter parameter. The vector is network reachable, low complexity, requires low privileges, needs no user interaction, and has high confidentiality impact with no stated integrity or availability impact.
Likely exposure
Exposure appears limited to Maarch RM 2.8 systems where authenticated users can access the statistics retrieval page. The affected-product metadata is incomplete, so inventory validation is required.
Exploitation context
The CVE is not listed as KEV, and the supplied sources do not state active exploitation. Public technical details exist, but this assessment does not include exploit instructions.
Researcher notes
The CVE record names Maarch RM 2.8 in the description but lists affected vendor/product as n/a. No official patch detail is included in the supplied bundle.
Mitigation direction
Check Maarch vendor guidance for fixed versions or official mitigations.
Restrict /statistics/retrieve access to trusted roles only.
Limit Maarch RM access to trusted networks where feasible.
Review authenticated user accounts for least-privilege access.
Monitor database and application logs for unusual statistics queries.
Validation and detection
Identify any Maarch RM 2.8 deployments in asset inventory.
Confirm whether authenticated users can reach /statistics/retrieve.
Review application logs for suspicious filter usage patterns.
Verify vendor advisories for patch status and affected versions.
Confirm database access is limited to required application privileges.
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.
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.
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.
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.
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.