LiveActive security incident?Get immediate response
CVE Record

CVE-2018-8070: QCMS version 3.0 has XSS via the title parameter to the /guest/index.html URI.

QCMS version 3.0 has XSS via the title parameter to the /guest/index.html URI.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2018-8070 is a reported cross-site scripting issue in QCMS 3.0. A page under /guest/index.html reportedly reflects the title parameter unsafely. If a public QCMS 3.0 site is exposed, attackers may be able to run script in a visitor's browser. Source evidence is sparse.

Executive priority

Prioritize remediation if QCMS 3.0 is internet-facing or used by authenticated staff. Otherwise, handle through normal legacy application risk reduction and migration planning.

Technical view

The CVE record describes XSS in QCMS version 3.0 through the title parameter on /guest/index.html. No CVSS score, CWE, vendor advisory, patch version, or affected CPE is provided in the source bundle. The linked reference appears to be the primary technical disclosure.

Likely exposure

Exposure is most likely limited to organizations still running QCMS 3.0 with the /guest/index.html route reachable by users or the internet.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. The public GitHub reference may contain proof-oriented details, but the provided evidence does not establish exploitation in the wild.

Researcher notes

The CVE metadata is minimal: no CVSS, CWE, vendor, CPE, or patch details are included. Treat the GitHub reference as the main disclosure source and avoid assuming broader product versions without confirmation.

Mitigation direction

  • Inventory any QCMS deployments and confirm whether version 3.0 is present.
  • Check QCMS project or vendor guidance for a patched release or official workaround.
  • Restrict public access to affected guest functionality if it is not required.
  • If maintaining the code, apply context-aware output encoding for the title value.
  • Consider adding CSP and WAF filtering as compensating controls.

Validation and detection

  • Confirm whether /guest/index.html exists on any QCMS 3.0 deployment.
  • Review application code handling of the title parameter for unsafe reflection.
  • Check web logs for unusual requests targeting the title parameter.
  • Verify any fix by confirming user-controlled title content is encoded, not executed.
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.

cve · low confidence lookup

CVE-2018-8070 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
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

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.