LiveActive security incident?Get immediate response
CVE Record

CVE-2020-19961: A SQL injection vulnerability has been discovered in zz cms version 2019 which allows attackers to retrieve...

A SQL injection vulnerability has been discovered in zz cms version 2019 which allows attackers to retrieve sensitive data via the component subzs.php.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-19961 is reported as a SQL injection in zz cms 2019. If exposed, an attacker may be able to retrieve sensitive database data through subzs.php. The public bundle does not provide CVSS scoring, confirmed fixed versions, or vendor mitigation details.

Executive priority

Prioritize scoping if zz cms 2019 is present, because SQL injection can lead to sensitive data exposure. If the product is absent, record non-exposure and monitor for updated vendor guidance.

Technical view

The issue is described as SQL injection affecting the subzs.php component in zz cms version 2019, with impact stated as sensitive data retrieval. The source bundle lacks CWE, CPE, CVSS, authentication requirements, exact vulnerable parameter details, and remediation status.

Likely exposure

Exposure is likely limited to organizations running zz cms version 2019, especially public-facing deployments where subzs.php is reachable. The bundle does not identify a formal vendor CPE or wider affected version range.

Exploitation context

The CVE is not listed as KEV in the supplied bundle. A public vulnerability write-up is referenced, but the bundle does not establish active exploitation, exploit maturity, authentication requirements, or real-world targeting.

Researcher notes

Evidence is sparse. The CVE description and referenced write-up support a SQL injection claim in subzs.php, but metadata is incomplete. Avoid assuming severity, affected ranges, exploitation, or a patch without additional vendor-confirmed information.

Mitigation direction

  • Inventory web assets for zz cms 2019 deployments.
  • Check the zzcms project or maintainer guidance for fixed versions.
  • Restrict public access to subzs.php where business allows.
  • Apply SQL injection protections in WAF or reverse proxy controls.
  • Review database exposure and least-privilege permissions for the application account.

Validation and detection

  • Confirm whether zz cms 2019 is present in production or staging.
  • Verify whether subzs.php is deployed and externally reachable.
  • Review web and database logs for suspicious requests or SQL errors.
  • Document current version, exposure path, and compensating controls.
  • Track vendor or project guidance before declaring remediation complete.
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-19961 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
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.