Security readout for executives and security teams
Plain-English summary
A malicious or compromised Snipe-IT superuser can abuse the Custom CSS setting to steal security tokens from other superusers. This could let the attacker take over privileged accounts and compromise asset-management data. The required superuser access narrows the attacker pool, but the potential impact remains critical.
Executive priority
Treat affected installations as an immediate remediation priority, especially where Snipe-IT contains sensitive asset data or has multiple superusers. Upgrade promptly, inspect Custom CSS, and investigate privileged-account activity. Internet exposure increases reachability, although exploitation still requires superuser privileges.
Technical view
Before version 8.7.0, Snipe-IT incompletely sanitizes Custom CSS by reversing HTML encoding for greater-than and double-quote characters. A superuser can store CSS using external @import or url() references and attribute selectors to disclose another superuser's CSRF token, potentially enabling account takeover.
Likely exposure
Organizations running Snipe-IT versions earlier than 8.7.0 are potentially affected. Exploitation requires an attacker-controlled superuser account, so compromised credentials, malicious administrators, and excessive superuser assignments are the principal exposure paths. The supplied evidence does not establish whether Custom CSS must already be enabled or separately configured.
Exploitation context
The vulnerability is remotely reachable through the application but requires high privileges. The supplied bundle does not identify public exploitation or confirmed attacks, and the CVE is not listed as KEV. A proof-of-concept or broader exploit availability is not established by the provided evidence.
Researcher notes
The key trust-boundary failure is allowing privileged stored CSS to influence another privileged user's browser. CVSS 4.0 is 9.3, with high confidentiality and integrity impacts across vulnerable and subsequent systems, but no stated availability impact. Validate sanitization behavior against the vendor patch without testing token exfiltration in production.
Mitigation direction
- Upgrade Snipe-IT to version 8.7.0 or later following vendor guidance.
- Review and remove untrusted Custom CSS before privileged users access the application.
- Restrict superuser accounts to essential personnel and investigate any unexpected privileged access.
- Review the vendor advisory and patch commit for deployment-specific remediation details.
Validation and detection
- Inventory every Snipe-IT instance and confirm its running version is 8.7.0 or later.
- Inspect Custom CSS for unexpected @import, url(), attribute selectors, or external domains.
- Review audit records for unauthorized Custom CSS changes and suspicious superuser activity.
- Check network telemetry for unexpected outbound requests triggered while superusers used Snipe-IT.
- After upgrading, confirm the installed build contains the vendor's sanitization fix.
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.
CWE-79: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-86738 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
- Critical
- CVSS
- 9.3 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
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.
SSVC decision data
CVSS vector scores
2 official scoresWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N——VulnCheckCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N2.35.8VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.3CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
Base CVSS 3.1 score
8.7HighVector: CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- GitHub Security Advisory (GHSA-pvcw-mp8q-mj39)CVE reference, VulnCheck · vendor-advisory
- Patch CommitCVE reference, VulnCheck · patch
- VulnCheck Advisory: Snipe-IT before 8.7.0 CSS Injection via Custom CSSCVE reference, VulnCheck · third-party-advisory
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.
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.