LiveActive security incident?Get immediate response
CVE Record

CVE-2020-22819: MKCMS V6.2 has SQL injection via the /ucenter/active.php verify parameter.

MKCMS V6.2 has SQL injection via the /ucenter/active.php verify parameter.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A flaw in MKCMS V6.2 may let unauthenticated internet users manipulate database queries through the account activation flow. That can expose or alter data and potentially disrupt service. The source bundle does not name a vendor fix, so remediation should start with confirming use and vendor guidance.

Executive priority

Prioritize any internet-facing MKCMS V6.2 instance for rapid verification and remediation planning. The technical impact is severe, but available sources do not confirm exploitation in the wild or provide a named patch.

Technical view

CVE-2020-22819 is CWE-89 SQL injection in MKCMS V6.2 through the verify parameter of /ucenter/active.php. The CVSS 3.1 vector indicates network access, low complexity, no privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely where MKCMS V6.2 is deployed and /ucenter/active.php is reachable. The bundle's structured affected product fields are n/a, so asset teams should verify technology use directly rather than rely only on CPE matching.

Exploitation context

The source bundle includes a public vulnerability write-up, but KEV is false and no cited source here confirms active exploitation. Treat internet-facing instances as urgent because the CVSS vector indicates unauthenticated remote reachability and high impact.

Researcher notes

Evidence is thin: the CVE description and blog reference identify the endpoint and parameter, while affected CPE data is absent. Do not infer other MKCMS versions or forks without separate evidence. Focus on asset discovery, route exposure, and vendor-supported remediation.

Mitigation direction

  • Identify whether MKCMS V6.2 is present in production or legacy environments.
  • Check MKCMS or project guidance for fixed versions or supported remediation.
  • Upgrade, replace, or retire affected MKCMS deployments based on vendor guidance.
  • Restrict public access to affected routes until remediation is confirmed.
  • Back up data and prepare recovery before making production changes.

Validation and detection

  • Inventory public web applications for MKCMS V6.2.
  • Confirm whether /ucenter/active.php is present and reachable.
  • Review web and database logs for unusual activation endpoint activity.
  • Verify remediation by vendor version or advisory confirmation.
  • Avoid validation methods that attempt SQL injection against production.
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.

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-22819 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
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

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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2020-22819Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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.