Summary
Snipe-IT versions before 8.6.3 contain an authorization bypass in the bulk user-delete functionality. A restricted user may be able to include user records outside their permitted scope, causing those accounts to be soft-deleted or disabled.
Affected context
The vulnerability occurs in Snipe-IT deployments where restricted users can access the bulk user-delete workflow. The risk is present when the server processes user identifiers supplied in a bulk operation without independently enforcing instance-level authorization for every targeted account.
Exploit preconditions
- Attack surface: Authenticated web application bulk user-management functionality
- Required access: A valid account with restricted administrative or user-management permissions
- Trigger point: Processing of a bulk delete request containing user records
- Why exploitation is possible: The bulk operation may trust submitted identifiers without applying the same authorization boundaries to each selected user
Why this happens
The underlying issue is an authorization enforcement gap in a bulk resource operation. The application accepts references to multiple user records but does not consistently verify that the requesting principal is allowed to modify every referenced account. This behavior maps to CWE-639: Authorization Bypass Through User-Controlled Key, where user-controlled object identifiers can be used to access or modify records outside the caller's permitted scope.
Potential impact
- Unauthorized users may soft-delete accounts outside their assigned scope
- Administrative or operational accounts could be disabled
- User access and availability may be disrupted
- Account-management records could be altered without proper authorization
- The incident could complicate recovery and audit investigations
General mitigation guidance
Mitigation generally focuses on enforcing authorization at the resource level for every item in a bulk request.
Common defensive patterns include:
- Rechecking ownership, tenancy, role, and scope permissions for each targeted user
- Deriving eligible record identifiers from server-side authorization queries rather than trusting client selections
- Rejecting mixed-scope bulk operations when any item is unauthorized
- Applying consistent authorization middleware to single-record and bulk endpoints
- Using least-privilege roles and limiting access to account-disabling functions
- Recording bulk actions with actor, target, scope, and outcome details for review
How teams detect issues like this
Organizations can look for this class of issue through:
- Static analysis of bulk endpoints that accept user-controlled record identifiers
- Code review checks comparing authorization in bulk handlers with single-record handlers
- Tests covering cross-scope, cross-tenant, and mixed-authority record selections
- Monitoring for bulk deletion events involving records outside the actor's normal administrative scope
- Policy enforcement requiring object-level authorization before state-changing operations
- Automated application security testing that evaluates access control across collections and individual resources

