LiveActive security incident?Get immediate response
CVE Record

CVE-2020-21228: JIZHICMS 1.5.1 contains a cross-site scripting (XSS) vulnerability in the component /user/release.html, whi...

JIZHICMS 1.5.1 contains a cross-site scripting (XSS) vulnerability in the component /user/release.html, which allows attackers to arbitrarily add an administrator cookie.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2020-21228 describes a cross-site scripting issue in JIZHICMS 1.5.1 at /user/release.html. The public summary says it could let an attacker add an administrator cookie, but the provided sources do not include CVSS scoring, affected CPEs, or a named fixed version.

Executive priority

Treat this as a targeted exposure-check item, not a confirmed emergency. Prioritize if JIZHICMS 1.5.1 is internet-facing or used for administrative workflows, because the reported impact concerns administrator cookies.

Technical view

The CVE record identifies an XSS vulnerability in JIZHICMS 1.5.1, specifically the /user/release.html component. Available metadata does not clarify whether the XSS is stored or reflected, does not assign CWE/CVSS data, and does not provide official remediation details beyond the referenced GitHub repository and issue.

Likely exposure

Exposure is limited to organizations running JIZHICMS, especially version 1.5.1, with the /user/release.html functionality reachable by users or attackers. The source bundle lists affected vendor and product as n/a, so asset confirmation is required.

Exploitation context

The source bundle does not show CISA KEV listing or cited evidence of active exploitation. The issue is publicly referenced on GitHub, but available evidence is too thin to claim exploit maturity or broad targeting.

Researcher notes

Evidence quality is limited. The CVE text names JIZHICMS 1.5.1 and /user/release.html, but lacks CVSS, CWE, CPE, exploit status, and remediation metadata. Avoid broad claims until the GitHub issue and local code are reviewed.

Mitigation direction

  • Inventory any JIZHICMS deployments and confirm exact versions.
  • Review the upstream repository and issue for maintainer guidance or fixed releases.
  • Restrict access to /user/release.html until remediation is confirmed.
  • Rotate administrator sessions if suspicious activity is found.
  • Retire or isolate unsupported instances if no fix can be confirmed.

Validation and detection

  • Confirm whether JIZHICMS 1.5.1 is present in production or staging.
  • Check whether /user/release.html is exposed to untrusted users.
  • Review web logs for unusual access to /user/release.html.
  • Review admin session and cookie activity for anomalies.
  • Perform authorized XSS regression testing without sharing payload 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.

cve · low confidence lookup

CVE-2020-21228 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.