Summary
Snipe-IT contains an authorization bypass in checkout-acceptance report actions when Full Multiple Company Support is enabled. An authenticated user with reports.view permission may enumerate acceptance identifiers and soft-delete records or trigger reminder emails for acceptances belonging to other companies.
Affected context
The vulnerability occurs in Snipe-IT deployments using Full Multiple Company Support and the checkout-acceptance report actions. It becomes risky when a user has permission to view reports but the action handlers do not consistently enforce the acceptance record's company boundary. The affected workflow may rely on a legacy users.company_id value that can be null, weakening authorization checks for records associated with other companies.
Exploit preconditions
- Attack surface: Authenticated checkout-acceptance report actions
- Required access: An account with the reports.view permission
- Deployment condition: Full Multiple Company Support must be enabled
- Trigger point: A report action that operates on a selected acceptance identifier
- Why exploitation is possible: Acceptance identifiers may be sequential, and a null-related company check can allow the action to proceed without confirming that the target belongs to the user's company
Why this happens
The underlying issue is an object-level authorization failure, mapping to CWE-639: Authorization Bypass Through User-Controlled Key. Report actions accept or derive a record identifier but do not reliably enforce ownership or tenant boundaries before performing the requested operation. A legacy nullable company relationship can cause the authorization condition to evaluate incorrectly, allowing a valid authenticated user to act on another company's acceptance record.
Potential impact
- An attacker may enumerate acceptance records across company boundaries
- An attacker could soft-delete checkout acceptance records belonging to another company
- Unauthorized reminder emails may be triggered for other companies' acceptances
- Audit accuracy and workflow integrity may be reduced
- Cross-tenant data exposure could occur through report behavior or resulting notifications
General mitigation guidance
Mitigation generally focuses on enforcing tenant-aware authorization at every report action, rather than relying only on report visibility permissions.
Common defensive patterns include:
- Checking the target record's company association before every read, update, deletion, or notification action
- Treating nullable or legacy ownership fields as an authorization failure unless ownership is explicitly established
- Using server-side object-level authorization instead of trusting submitted identifiers
- Avoiding sequential identifiers as the sole basis for access decisions
- Applying least privilege to report and workflow actions
- Preserving audit logs for cross-company authorization failures and administrative actions
How teams detect issues like this
Organizations can look for this class of issue through:
- Static analysis and code review rules requiring tenant checks before record mutations or notifications
- Tests that exercise every report action with records from the same and different companies
- Review signals involving nullable ownership fields, legacy company columns, and direct identifier lookups
- Authorization policies that require explicit object-level and tenant-level checks
- Monitoring for repeated requests involving sequential acceptance identifiers or cross-company action failures
Automated application security and code review tools may help identify missing authorization checks, but business-logic tests remain important.

