LiveActive security incident?Get immediate response
CVE Record

CVE-2020-36537: Everywhere CMS sql injection

A vulnerability was found in Everywhere CMS. It has been classified as critical. Affected is an unknown function. The manipulation of the argument id leads to sql injection. It is possible to launch the attack remotely.

MediumCVSS 6.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-36537 is a SQL injection issue in Everywhere CMS. A remote user with low privileges may manipulate an id argument to affect the database. The public record does not identify exact versions, the vulnerable function, or a fixed release.

Executive priority

Handle as a moderate-priority exposure review. The issue can affect database confidentiality, integrity, and availability, but current public evidence lacks active exploitation, exact version scope, and patch details.

Technical view

The CVE maps to CWE-89 and has CVSS 3.1 score 6.3. The vector is network-accessible, low attack complexity, low privileges required, no user interaction, unchanged scope, with low confidentiality, integrity, and availability impact.

Likely exposure

Organizations running Everywhere CMS may be exposed, but the source bundle does not provide CPEs, exact affected versions, or affected routes. Treat any active deployment as requiring vendor verification.

Exploitation context

The bundle says remote exploitation is possible, but KEV is false and no cited source establishes active exploitation. Do not assume exploitation in the wild without additional evidence.

Researcher notes

Evidence is thin: affected function and versions are unknown, and no CPEs are listed. The strongest confirmed facts are product, argument name, CWE-89 classification, CVSS vector, remote reachability, and low-privilege requirement.

Mitigation direction

  • Inventory any Everywhere CMS deployments and owners.
  • Check CVE, vendor, and VulDB guidance for fixed versions or workarounds.
  • Limit network access to trusted users until exposure is clarified.
  • Prioritize replacement or isolation if the CMS is unsupported.
  • Review database and application logs for suspicious id-parameter activity.

Validation and detection

  • Confirm whether Everywhere CMS is present in production or staging.
  • Determine deployed version and compare it with vendor guidance when available.
  • Review application paths that accept an id argument.
  • Check logs for SQL errors or unusual requests involving id.
  • Verify remediation with regression tests for id input handling.
Prepared
Confidence
medium
Sources
3

Public sources used

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-2020-36537 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
Medium
CVSS
6.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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
2Source 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
6.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L2.83.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

6.3Medium
CVSS 3.1 vector shape for CVE-2020-36537Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
EverywhereCMSn/aListed
Weakness

CWE details

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