LiveActive security incident?Get immediate response
CVE Record

CVE-2020-18106: The GET parameter "id" in WMS v1.0 is passed without filtering, which allows attackers to perform SQL injec...

The GET parameter "id" in WMS v1.0 is passed without filtering, which allows attackers to perform SQL injection.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-18106 describes a SQL injection issue in WMS v1.0 where an unfiltered GET parameter named id can reach database logic. If a deployed instance is vulnerable, an attacker could potentially interfere with database-backed data. The public record does not provide severity, CVSS, CPEs, or confirmed exploitation.

Executive priority

Treat this as an inventory-driven risk. SQL injection can be serious, but the public record is sparse and does not confirm exploitation or a patch. Prioritize quickly determining whether affected code exists and whether it is reachable from untrusted users.

Technical view

The CVE states that WMS v1.0 passes the GET id parameter without filtering, enabling SQL injection. The source bundle lists no CVSS score, CWE mapping, vendor, product CPE, patch version, or mitigation. The only external reference provided is a GitHub issue for FeMiner/wms.

Likely exposure

Exposure appears limited to organizations running WMS v1.0 or related FeMiner/wms code. Exact affected product metadata is incomplete in the CVE record, so teams should verify whether this code exists in production, staging, or inherited application forks.

Exploitation context

The source bundle does not show CISA KEV listing or any cited evidence of active exploitation. A public GitHub issue exists, which means the vulnerability information is publicly accessible, but exploit status is not established by the provided sources.

Researcher notes

Evidence is limited: no CVSS, CWE, CPEs, or patch reference are present in the supplied CVE data. The affected field says n/a, while the title and GitHub reference identify WMS v1.0 and FeMiner/wms context. Avoid assuming broader product impact.

Mitigation direction

  • Identify any WMS v1.0 or FeMiner/wms deployments or forks.
  • Check the project issue and vendor guidance for an official fix.
  • Restrict public access to affected WMS routes where possible.
  • Use parameterized database queries for any id-driven lookups.
  • Monitor web and database logs for suspicious id parameter activity.

Validation and detection

  • Confirm whether WMS v1.0 or FeMiner/wms code is deployed.
  • Review GET id handling for direct database query construction.
  • Verify database queries use bound parameters, not string concatenation.
  • Check logs for database errors tied to id requests.
  • Document whether exposure is internet-facing, internal, or absent.
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-18106 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.