CVE Intelligence
High Cross-site scripting exploit reference

CVE-2026-62368 — Cross-site Scripting (XSS) in Snipeitapp Snipe-it

Snipe-IT is an IT asset/license management system. Prior to 8.7.0, a user with the customfields.create permission can store markup in CustomField.name, and app/Presenters/AssetPresenter.php assigns that value as an unescaped bootstrap-table header title. When another user opens an asset-list page associated with the fieldset, the stored markup executes on page load in that user's Snipe-IT session. This can expose same-origin data and perform authenticated actions with the victim's privileges, including privilege escalation when a superuser views the affected list. This issue is fixed in version 8.7.0.

Published Sep 24, 2026 · Updated Oct 15, 2026 · Sources: NIST National Vulnerability Database · CNA: security-advisories@github.com

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
—
No EPSS score.
Affects
Snipeitapp
Snipe-it
CVSS base
8.4
High · 2 source(s)

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — github.com (NIST National Vulnerability Database)
  • Documented patch — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Snipeitapp Snipe-it).
  2. Apply the fixed version or the patch documented under Remediation.
  3. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  4. Search available logs for exploit probes matching the vulnerability class (cross-site scripting), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Snipeitapp Snipe-it < 8.7.0 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.4 CVSS 3.1 High 1.7 6.0 nvd@nist.gov via NIST National Vulnerability Database
8.1 CVSS 3.1 High 1.7 5.8 security-advisories@github.com via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 8.4 (NVD (NIST)) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-79 · Cross-site Scripting (XSS)

Other CVEs with this weakness →

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Monitor CSP violation reports and script payloads in reflected parameters.
web/proxy/WAF logsnetwork IDS/IPSapplication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Record published
    Oct 15, 2026
  • Fix documented
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVSS changed · 8.4
    Oct 15, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 15, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 15, 2026 · NIST National Vulnerability Database
  • CVE published
    Sep 24, 2026 · security-advisories@github.com

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 15, 2026 – Oct 15, 2026

References

3 on the record

Elsewhere on this site

Snipeitapp
every CVE for this vendor
Cross-site scripting
same class
CWE-79
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-63498 Cross-site Scripting (XSS) in Snipeitapp Snipe-it 21d
  • CVE-2026-63493 Authentication Bypass Using an Alternate Path or Channel in Snipeitapp Snipe-it 21d
  • CVE-2026-88894 Incorrect Authorization in Snipeitapp Snipe-it Sep 10, 2026
  • CVE-2026-86774 Improper Access Control in Snipeitapp Snipe-it Sep 9, 2026
  • CVE-2026-86773 Incorrect Authorization in Snipeitapp Snipe-it Sep 9, 2026
  • CVE-2026-86768 Improper Input Validation in Snipeitapp Snipe-it Sep 9, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No FIRST EPSS score.
  • No CISA SSVC assessment.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-62368 is "Cross-site Scripting (XSS) in Snipeitapp Snipe-it", rated High. It affects Snipe-it (Snipeitapp); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.4 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.