LiveActive security incident?Get immediate response
CVE Record

CVE-2020-23450: Spiceworks Version <= 7.5.00107 is affected by XSS.

Spiceworks Version <= 7.5.00107 is affected by XSS. Any name typed on Custom Groups function is vulnerable to stored XSS as they displayed on http://127.0.0.1/inventory/groups/ without output sanitization.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2020-23450 is a stored cross-site scripting issue in Spiceworks versions up to 7.5.00107. A Custom Groups name may be stored and later displayed on the inventory groups page without sanitization. Sources do not provide CVSS scoring, patch details, or evidence of active exploitation.

Executive priority

Treat this as a moderate hygiene and internal-application risk. Prioritize remediation if Spiceworks is still deployed, especially where helpdesk or inventory administrators use shared privileged sessions.

Technical view

The reported flaw is stored XSS in the Custom Groups function. Unsanitized group names are rendered at /inventory/groups/, allowing script content to persist and execute when viewed. The CVE record gives limited product metadata and no CWE, CVSS vector, fixed version, or vendor mitigation.

Likely exposure

Exposure is likely limited to organizations still running Spiceworks version 7.5.00107 or earlier and using the Custom Groups inventory feature. Internet exposure is not established by the sources.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation. Exploitation would require the ability to create or modify a Custom Groups name and have another user view the affected groups page.

Researcher notes

Evidence is thin: the CVE cites stored XSS behavior but lacks CVSS, CWE, authenticated status, patch information, and detailed affected product metadata. Avoid asserting broader Spiceworks product exposure beyond version <= 7.5.00107.

Mitigation direction

  • Identify Spiceworks deployments and versions; prioritize version 7.5.00107 or earlier.
  • Check official Spiceworks guidance for fixed versions or supported workarounds.
  • Restrict Custom Groups management to trusted administrators only.
  • Limit access to the inventory groups page to authorized internal users.
  • Review and remove suspicious Custom Groups names.

Validation and detection

  • Confirm whether any Spiceworks instance is version 7.5.00107 or earlier.
  • Determine who can create or edit Custom Groups names.
  • Review existing Custom Groups names for unexpected markup or script-like content.
  • Check whether /inventory/groups/ is reachable beyond intended users.
  • Document patch or compensating-control status for each instance.
Prepared
Confidence
low
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-23450 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.