Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-61807 medium CVSS 6.1

Cross-Site Scripting (XSS) in snipe/snipe-it (CVE-2026-61807)

Summary

Cross-site scripting in snipe/snipe-it (CVE-2026-61807). Risk of unauthorized operations or information disclosure. Exploitable via b224cc636c6780386e3f73f03d1171f52ab4c37a. Mitigation: upgrade to 8.6.2 or later.

Original description

The description as published by the source.

Impact

The table component derives data-selected-count-id from the component $name value. On manufacturer and supplier detail pages, stored manufacturer or supplier names are passed into affected table components as that name value. The client-side JavaScript later reads the browser-decoded data-selected-count-id, uses it as a selector, and concatenates countId.substring(1) directly into an HTML string passed to jQuery .after().

Affected commit:

b224cc636c6780386e3f73f03d1171f52ab4c37a

Example payload for a manufacturer or supplier name:
x[foo=">"]>

The issue appears to involve the following flow:

Stored supplier/manufacturer name
-> table component data-selected-count-id
-> browser decodes the attribute
-> JavaScript reads countId
-> countId is used as a selector
-> countId.substring(1) is concatenated into HTML
-> jQuery .after() inserts attacker-controlled markup
-> JavaScript executes in the victim's browser

Potential impact includes arbitrary JavaScript execution in the browser of an authenticated Snipe-IT user who views the affected supplier or manufacturer detail page. If the victim has elevated privileges, this may allow access to data or actions available to that user's session.

Patches

Patched in https://github.com/grokability/snipe-it/commit/d12ad3d53869443b96b663ba3ce2673ef343da71

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-61807 has been found in snipe/snipe-it.
Attackers can target a specific entry point like b224cc636c6780386e3f73f03d1171f52ab4c37a over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.1/10.
What to do: upgrade snipe/snipe-it to 8.6.2 or later.
If unsure, ask your IT team or search "snipe/snipe-it CVE-2026-61807" on the vendor's site.

CVE-2026-61807 (snipe/snipe-it) — CWE-79 / CVSS v3 6.1
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: b224cc636c6780386e3f73f03d1171f52ab4c37a
Patched: 8.6.2 — 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.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in snipe/snipe-it. Attackers reach the vulnerable code path via b224cc636c6780386e3f73f03d1171f52ab4c37a without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of snipe/snipe-it. Attack surface: b224cc636c6780386e3f73f03d1171f52ab4c37a.

🔥 Severity

Severity: Medium (CVSS 6.1/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 8.6.2.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. 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

  1. 1
    Identify exposure identify 
    grep -r 'snipe/snipe-it' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で snipe/snipe-it を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade snipe/snipe-it to 8.6.2

    ステージング環境で 8.6.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

composer snipe/snipe-it
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.6.2"}]}]
Packagist snipe/snipe-it
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"8.6.2"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details