CVE-2026-55466: Snipe-IT vulnerable to stored XSS via inline-served attachment
Impact A low-privilege user can store an active-content payload as an asset attachment and have it served inline, same-origin, with an active Content-Type, achieving stored XSS. The application sanitizes uploads only when PHP finfo detects image/svg+xml.
Published Aug 28, 2026
Affected packages
snipe/snipe-it
- Ecosystem
- Composer (PHP)
- Affected
- <= 8.6.1
- Fixed in
- 8.6.2
- Check
composer show snipe/snipe-it
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Impact
A low-privilege user can store an active-content payload as an asset attachment and have it served inline, same-origin, with an active Content-Type, achieving stored XSS. The application sanitizes uploads only when PHP finfo detects image/svg+xml. By submitting an XHTML document whose finfo MIME is text/xml (an allowed extension), the svg-sanitize branch is skipped, the is stored raw, and the inline-serve path returns it as text/xml; charset=utf-8 with Content-Disposition: inline — which the browser renders as a live XHTML document and executes. The dedicated StorageHelper::allowSafeInline() whitelist that should have constrained inline-renderable types is never wired into the serve path.
Details
Vulnerable code — sanitizer keyed on finfo MIME app/Http/Requests/UploadFileRequest.php:46-53
$extension = $file->getClientOriginalExtension();
$file_name = $name_prefix.'-'.str_random(8).'-'.str_slug(...).'.'.$file->guessExtension();
...
if ($file->getMimeType() === 'image/svg+xml') {
$uploaded_file = $this->handleSVG($file); // svg-sanitize fires
} else {
$uploaded_file = file_get_contents($file); // stored RAW — no sanitization
}Vulnerable code — inline serve, no allowSafeInline() app/Http/Controllers/UploadedFilesController.php:103
if (request('inline') == 'true') {
$headers = ['Content-Disposition' => 'inline'];
return Storage::download($path.$log->filename, $log->filename, $headers);
}StorageHelper::allowSafeInline() (app/Helpers/StorageHelper.php:88) exists to whitelist inline-renderable types but is not called here. The validation rule (UploadFileRequest::rules()) is mimes: over config('filesystems.allowed_upload_extensions_for_validator'), which includes svg, xml, and txt — so a text/xml file passes validation and bypasses the SVG sanitizer simultaneously.
POC
- From a fresh install, as a user with only
assets.view+assets.filestargeting any existing asset created by admin - click on the asset created by admin and upload files.
- create a XML file with the following payload and upload it.
<?xml version="1.0"?>
<html xmlns="http://www.w3.org/1999/xhtml">
<head><script>alert(document.cookie)</script></head>
<body>hi</body>
</html>- Noticed that it did not receive any error and the file was uploaded.
- Now, can just get the URL and view it. (need to add the
inline=true).
image.png
Notice that the XSS was able to request document.cookie. This means that it is possible for low privilege user to perform XSS and perform privilege escalation to admin.
Credited to callmeks.
References
- https://github.com/grokability/snipe-it/security/advisories/GHSA-jhph-5q74-pmfx
- https://nvd.nist.gov/vuln/detail/CVE-2026-55466
- https://github.com/grokability/snipe-it/commit/000cea0a622d586366cf60d2240c7c2a4b17c955
- https://github.com/grokability/snipe-it/releases/tag/v8.6.2
- https://github.com/advisories/GHSA-jhph-5q74-pmfx
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-62368
Snipe-IT: Stored XSS via Custom Field name in asset-list column headers
high8.1Sep 24, 2026CVE-2026-63493
Snipe-IT: 2FA bypass via the API token flow
high8.6Sep 24, 2026CVE-2026-63498
Snipe-IT: Stored XSS via Inline XML Rendering in the Uploaded Files API
high8.7Sep 24, 2026CVE-2026-55452
Snipe-IT has CSV formula injection in Activity Report export
medium4.8Aug 28, 2026CVE-2026-55460
Snipe-IT has an authorization bypass on bulk editing users
high7.1Aug 28, 2026CVE-2026-55461
Snipe-IT has an Open Redirect After User Edit
medium6.1Aug 28, 2026
