PatchClock

PHP security digest · 24 Sep 2026

Snipe-IT: Stored XSS via Custom Field name in asset-list column headers

High CVE-2026-62368

Package
snipe/snipe-it
Fixed in
8.7.0
Published
Thu 24 Sep 2026, 19:19 LisbonUpdated Mon 26 Oct 2026, 01:25 Lisbon
Installs on Packagist
731

In plain words

A user with the customfields.create permission can save malicious script in a Custom Field name that is later shown as an asset-list column heading. The script runs automatically when anyone opens the asset list, including a superuser. This can let a lower-privileged user gain superuser privileges.

Affected versions

PackageAffectedFixed in
snipe/snipe-it< 8.7.08.7.0

Am I affected?

Check composer.lock for snipe/snipe-it: versions below 8.7.0 are affected, and 8.7.0 is fixed. Check who has the customfields.create permission and whether Custom Fields are added to fieldsets associated with asset models, so their names appear as asset-list column headings, for example on /hardware.

What to do

Check which version you have, then update to a fixed release for your branch (8.7.0):

composer show snipe/snipe-it | grep versions
composer update snipe/snipe-it

If your version constraint in composer.json keeps you below a fixed release, raise it first. Whether your configuration is affected, and the exact version ranges, are in the advisory itself.

The advisory's description

Impact

A user with the "customfields.create" permission can store HTML/JS in a Custom Field name, which is later rendered as an asset-list column title WITHOUT escaping at app/Presenters/AssetPresenter.php line 364 ('title' => $field->name) and injected into the table header by the bundled bootstrap-table plugin. It executes for anyone who opens an asset list (e.g. /hardware), including superusers, on page load with no interaction. Since "customfields.create" can be granted to non-superusers, a lower-privileged user gets script execution in a superuser's session -> privilege escalation.

STEPS TO REPRODUCE

  1. As a user with "customfields.create", create a Custom Field named: <img src=x onerror=alert(1)>
  2. Add the field to a fieldset that is associated with an asset model.
  3. Open /hardware -> the payload executes on load.

DEMONSTRATED IMPACT An account holding ONLY "customfields.create" (HTTP 403 on /users) planted a payload that, when a superuser opened /hardware, issued an authenticated request in that session and granted the attacker's own account the "superuser" permission (afterwards: GET /users = 200, isSuperUser() = true).

ROOT CAUSE

  • Blade {{ }} encodes the data-columns attribute, but the browser decodes it back before bootstrap-table reads the title; bootstrap-table then renders the header title unescaped because its table-level "escape" option defaults to false and is never enabled. (The per-column 'escape' => true covers cell values, not the header title.)

Patches

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

Weakness: CWE-79 Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'). Reported by Mickey777777.

The advisory

From OSV.dev, which gathers the GitHub Advisory Database, FriendsOfPHP and Drupal security advisories; the summary is theirs. The description, affected versions, weakness and credits are from the GitHub Advisory Database (CC BY 4.0). "In plain words", "Am I affected?" and "If you cannot update yet" are based on that advisory, and checked to name no version it does not.