Summary
A missing authorization control in the Snipe-IT Accessories API allows low-privileged users to create accessory records under companies they do not belong to when Full Multiple Companies Support is enabled.
By mass-assigning the company_id attribute, an attacker can bypass tenant isolation and inject data into other companies' asset inventories.
Affected context
This vulnerability appears in deployments of Snipe-IT where:
- Full Multiple Companies Support is enabled to support multi-tenant use,
- The Accessories API create endpoint is exposed to authenticated users with limited roles,
- The
company_idfield on the Accessory model is mass-assignable and not constrained by per-request authorization checks.
In such environments, accessory creation requests can be crafted to associate new records with a different company than the one the user is legitimately assigned to.
Exploit preconditions
- Attack surface: Snipe-IT Accessories API create endpoint.
- Required access: Authenticated, low-privileged account belonging to at least one company in a multi-company deployment.
- Trigger point: Submission of an accessory creation request that includes a
company_idvalue for a company the user should not control. - Why exploitation is possible: The server-side logic relies on mass assignment of request parameters into the Accessory model without enforcing that
company_idaligns with the authenticated user's allowed companies, effectively omitting a critical authorization check (CWE-862).
Why this happens
The underlying issue is a missing authorization validation on a sensitive, tenant-scoping field (company_id) during mass assignment.
The Accessories API directly maps incoming request parameters to model attributes, trusting the client to supply a legitimate company_id value.
Because the application does not verify that this value belongs to a company the user is authorized to act for, attackers can cross company boundaries and create data in other tenants' scopes.
This aligns with CWE-862: Missing Authorization, where operations are allowed based solely on authentication without enforcing resource-level access control.
Potential impact
- Attackers could create accessory records under other companies' inventories.
- Cross-tenant data pollution may occur, complicating asset tracking and reporting.
- Malicious or misleading records can be introduced into another company's asset management workflows.
- Indirect integrity issues may arise if downstream processes or integrations trust accessory data to be tenant-isolated.
General mitigation guidance
Effective mitigation focuses on enforcing strict, server-side authorization around tenant-scoping fields and limiting mass assignment:
- Treat fields such as
company_idas server-controlled, deriving their values from the authenticated user's context rather than trusting client input. - Introduce explicit authorization checks that validate whether the user is allowed to operate on a specific company before persisting any record.
- Constrain mass assignment so that only non-sensitive attributes are bindable from request parameters, using explicit whitelists or dedicated DTOs.
- Apply a consistent multi-tenant access control pattern, ensuring every create, update, and delete operation is scoped to the user's permitted companies by default.
How teams detect issues like this
Organizations can detect similar issues by:
- Reviewing API controllers and services for operations where client-supplied identifiers (such as
company_id,tenant_id, or organization IDs) are directly assigned to models without authorization checks. - Using static analysis or linters configured to flag mass-assignment on fields marked as tenant- or ownership-scoping.
- Implementing code review checklists that explicitly call out the need to verify tenant isolation and resource-level authorization for all multi-tenant operations.
- Adding automated tests that attempt to perform cross-company operations with low-privileged accounts to validate isolation guarantees.

