LiveActive security incident?Get immediate response
CVE Record

CVE-2020-23630: A blind SQL injection vulnerability exists in zzcms ver201910 based on time (cookie injection).

A blind SQL injection vulnerability exists in zzcms ver201910 based on time (cookie injection).

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-23630 describes a blind, time-based SQL injection issue in zzcms ver201910 through cookie handling. The sources do not provide a CVSS score, vendor advisory, confirmed patch, or evidence of active exploitation. Treat exposed deployments seriously because SQL injection can affect data confidentiality and integrity.

Executive priority

Prioritize inventory first, then containment for any internet-facing zzcms ver201910 system. Business urgency depends on whether the product is deployed and whether it stores sensitive or regulated data.

Technical view

The CVE record states that zzcms ver201910 has a time-based blind SQL injection vulnerability involving cookie injection. Public references point to a GitHub proof report, but the bundle does not include affected CPEs, CWE mapping, vulnerable parameter details, or remediation guidance.

Likely exposure

Organizations are likely exposed only if they run zzcms ver201910, especially on internet-facing systems. The provided CVE metadata does not identify vendor CPEs or broader affected versions.

Exploitation context

CISA KEV status is false, and the bundle provides no cited evidence of active exploitation. The public GitHub issue indicates vulnerability disclosure details exist, but this analysis does not rely on weaponization steps.

Researcher notes

Evidence is thin: no CVSS vector, CWE, CPE, patch reference, or vendor advisory is present in the bundle. The key confirmed claim is a time-based blind SQL injection in zzcms ver201910 involving cookies.

Mitigation direction

  • Identify any zzcms ver201910 deployments in production, staging, and legacy hosting.
  • Check the zzcms project or vendor channels for fixed releases or official guidance.
  • Restrict public access to affected instances where business requirements allow.
  • Increase monitoring for suspicious cookie-bearing requests and database timing anomalies.
  • Retire or isolate unsupported zzcms ver201910 deployments if no fix is available.

Validation and detection

  • Confirm application version through deployment records, package files, or administrator inventory.
  • Map whether any zzcms ver201910 instance is internet-facing or handles sensitive data.
  • Review web and database logs for unusual delayed responses tied to cookie-bearing requests.
  • Track the CVE record and referenced GitHub issue for updated remediation details.
Prepared
Confidence
medium
Sources
4

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-23630 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
3Timeline events
1ADP providers
3Source links

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CVECVE Program Container

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.