# CVE-2026-62368: Snipe-IT: Stored XSS via Custom Field name in asset-list column headers

> Attackers with custom field creation rights can inject scripts into asset list headers, leading to session hijacking or privilege escalation when viewed by other users.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-p9h3-gvpq-5539

## What is CVE-2026-62368?

CVE-2026-62368 is a high-severity cross-site scripting vulnerability in Snipeitapp Snipe-It, published on 24 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-62368?

2 open source packages ship an affected version, including snipe/snipe-it. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `snipe/snipe-it` | Packagist | All versions | 8.7.0 |
| `snipe/snipe-it` | Packagist | All versions | 8.7.0 |

Products: Snipeitapp Snipe-It.

## How do I fix CVE-2026-62368?

Upgrade snipe/snipe-it to 8.7.0 or later.

## Is CVE-2026-62368 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62368 exists.

## Other vulnerabilities in Snipeitapp Snipe-It

- [CVE-2025-63601](https://insights.sbomify.com/CVE-2025-63601/): File upload in n/a (critical 9.9)
- [CVE-2026-37709](https://insights.sbomify.com/CVE-2026-37709/): Snipe-IT has insecure permissions in file uploads (critical 9.8)
- [CVE-2026-86738](https://insights.sbomify.com/CVE-2026-86738/): Snipe-IT before 8.7.0 CSS Injection via Custom CSS (critical 9.3)
- [CVE-2026-116199](https://insights.sbomify.com/CVE-2026-116199/): Snipe-IT before 8.6.3 Authentication Bypass via Google SSO Callback (critical 9.2)
- [CVE-2022-1380](https://insights.sbomify.com/CVE-2022-1380/): Stored Cross Site Scripting vulnerability in Item name parameter in snipe/snipe-it (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-62368 and fix it if it is affected.

What it is: CVE-2026-62368 is a high-severity cross-site scripting vulnerability in Snipeitapp Snipe-It, published on 24 Sep 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-62368 exists.

Affected packages and fixed versions:
- snipe/snipe-it (Packagist): affected all versions; fixed in 8.7.0
- snipe/snipe-it (Packagist): affected all versions; fixed in 8.7.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-62368/ (Markdown: https://insights.sbomify.com/CVE-2026-62368/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-62368
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-62368
- OSV: https://osv.dev/vulnerability/CVE-2026-62368

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-62368/
Summaries are generated and may contain mistakes; the official description above is the record.