Security readout for executives and security teams
Plain-English summary
ZrLog 2.0.3 has a stored cross-site scripting issue in its file upload area. A crafted uploaded file pathname can be saved and later cause script execution when viewed. The sources do not provide CVSS, a vendor patch version, or evidence of active exploitation.
Executive priority
Treat this as a focused web application risk. Prioritize systems that expose ZrLog upload workflows to untrusted users or where administrators regularly review uploaded files.
Technical view
CVE-2018-17421 describes stored XSS in ZrLog 2.0.3 through a crafted attached/file/ pathname in the upload area. The record lacks CWE, CVSS, CPE, and fixed-version metadata. Validation should focus on whether ZrLog 2.0.3 is deployed and whether uploaded file pathnames are rendered unsafely.
Likely exposure
Exposure is likely limited to environments running ZrLog 2.0.3 with reachable file upload and management views. The provided data does not identify other affected versions or products.
Exploitation context
No CISA KEV listing is provided, and the source bundle does not cite active exploitation. Stored XSS can still create risk if administrators or users view attacker-controlled uploaded file metadata.
Researcher notes
The evidence is sparse: one CVE record and a GitHub issue reference. The affected version is stated as ZrLog 2.0.3, but no CVSS, CWE, CPE, patch, or exploit telemetry is included.
Mitigation direction
- Check upstream ZrLog guidance and release notes for an official fix.
- Upgrade only to a version the vendor identifies as fixed.
- Restrict upload capability to trusted authenticated users.
- Review and remove uploaded entries with suspicious pathnames.
- Apply output encoding for displayed upload pathnames in maintained forks.
Validation and detection
- Inventory web applications for ZrLog 2.0.3 deployments.
- Confirm whether file upload functionality is enabled and reachable.
- Review uploaded file metadata for crafted or unusual pathnames.
- Check whether upload pathnames are rendered as executable HTML or script.
- Verify any deployed fix against vendor guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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.
File access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2018-17421 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/94fzb/zrlog/issues/39CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.