Cross-Site Scripting (XSS) in snipe/snipe-it (CVE-2026-63498)
Summary
Cross-site scripting in snipe/snipe-it (CVE-2026-63498). Confidential information can be exposed externally. Exploitable via GET /api/v1/{object_type}/{id}/files/{file_id}. Mitigation: upgrade to 8.7.0 or later.
Original description
The description as published by the source.
Snipe-IT's uploaded-files API accepts XML documents and later serves them inline without applying the safe-inline allowlist used by the equivalent web controller. An authenticated user who can attach files to a supported object can upload an XSLT stylesheet and an XML document that references it through xml-stylesheet. When another authorized user opens the XML file through the API with ?inline=true, the browser applies the attacker-controlled stylesheet, which produces HTML containing JavaScript in the Snipe-IT origin.
This was reproduced against commit df8e3b144331d0c1cc14778f900e7646d1d9a509 (v8.6.3-231-gdf8e3b1443).
The attack requires an authenticated account with file access to at least one supported object and one victim interaction. Scope changes because attacker-controlled code executes in another user's Snipe-IT security context. The script can read same-origin data available to the victim and perform authenticated actions as that victim.
Affected Components
- app/Http/Requests/UploadFileRequest.php
Allows xml uploads through filesystems.allowed_upload_extensions_for_validator.
Sanitizes only files detected as image/svg+xml. Both files in this proof of concept are detected by PHP finfo as text/xml, so they are stored unchanged. - config/filesystems.php
Includes xml in allowed_upload_extensions_array. - app/Http/Controllers/Api/UploadedFilesController.php, method show()
Honors the attacker-controlled inline=true query parameter for every uploaded file type.
Ca…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-63498 has been found in snipe/snipe-it.
Attackers can target a specific entry point like GET /api/v1/{object_type}/{id}/files/{file_id} over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade snipe/snipe-it to 8.7.0 or later.
If unsure, ask your IT team or search "snipe/snipe-it CVE-2026-63498" on the vendor's site.
CVE-2026-63498 (snipe/snipe-it) — CWE-79 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Attack surface: GET /api/v1/{object_type}/{id}/files/{file_id}
Patched: 8.7.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Cross-site scripting (XSS) (CWE-79) exists in snipe/snipe-it. Attackers reach the vulnerable code path via GET /api/v1/{object_type}/{id}/files/{file_id}.
Check the vendor advisory for the affected versions of snipe/snipe-it. Attack surface: GET /api/v1/{object_type}/{id}/files/{file_id}.
Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.
Update to 8.7.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual GET /api/v1/{object_type}/{id}/files/{file_id} requests with malformed payloads or SQL meta-characters. Run grep -r 'snipe/snipe-it' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'snipe/snipe-it' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
snipe/snipe-itを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'GET /api/v1/{object_type}/{id}/files/{file_id}' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
GET /api/v1/{object_type}/{id}/files/{file_id}への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade snipe/snipe-it to 8.7.0ステージング環境で 8.7.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against GET /api/v1/{object_type}/{id}/files/{file_id} on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web github.com