LiveActive security incident?Get immediate response
CVE Record

CVE-2020-20392: SQL Injection vulnerability in imcat v5.2 via the fm[auser] parameters in coms/add_coms.php.

SQL Injection vulnerability in imcat v5.2 via the fm[auser] parameters in coms/add_coms.php.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-20392 describes a SQL injection issue in imcat v5.2. If an organization runs this software and the affected add_coms endpoint is reachable, an attacker may be able to manipulate database queries. Public evidence is sparse, with no CVSS score, KEV listing, or named fix in the provided sources.

Executive priority

Prioritize investigation if imcat v5.2 is internet-facing or supports sensitive data. With no severity score or confirmed exploitation in the provided sources, urgency depends on whether the affected software and endpoint exist in your environment.

Technical view

The CVE record identifies SQL injection in imcat v5.2 via the fm[auser] parameter in coms/add_coms.php. The provided record has no CVSS, CWE, structured affected CPEs, or remediation details. Treat exposure as application-specific until the deployed version and reachable route are confirmed.

Likely exposure

Likely exposure is limited to systems running imcat v5.2 with coms/add_coms.php accessible. The CVE affected-product fields are n/a, so vulnerability managers should confirm software presence through inventory, source review, or deployment records rather than relying on CPE matching.

Exploitation context

The provided sources do not show CISA KEV inclusion or confirmed active exploitation. The public reference is a GitHub issue. SQL injection is a serious vulnerability class, but the available evidence does not establish exploit maturity, authentication requirements, or real-world abuse.

Researcher notes

Evidence is minimal: the CVE description and referenced GitHub issue identify the parameter and file path, but not impact depth, privileges, patch status, or exploit status. Avoid assuming broader imcat versions are affected without vendor or code evidence.

Mitigation direction

  • Check imcat project guidance and issue tracker for fixed versions or patches.
  • Restrict access to the affected add_coms functionality until remediation is confirmed.
  • Review application logs for suspicious requests to coms/add_coms.php.
  • Ensure the application database account uses least-privilege permissions.
  • Apply any vendor-confirmed fix after testing in a non-production environment.

Validation and detection

  • Confirm whether imcat v5.2 is deployed in any environment.
  • Identify whether coms/add_coms.php is reachable from untrusted networks.
  • Review fm[auser] handling for parameterized database access.
  • Check logs for unusual input patterns targeting the affected endpoint.
  • Verify any remediation against vendor guidance in a test environment.
Prepared
Confidence
medium
Sources
3

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.

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-2020-20392 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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