Skip to content

GHSA-pwpj-p52h-q484 CVE-2026-54329

Snipe-IT API Vulnerable to Cross-Tenant Accessory Injection

High Packagist
Severity
8.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.39%
Chance of exploitation in the next 30 days. Higher than 32.98% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Fix
8.6.2
Upgrade snipe/snipe-it to this version or later

Description

Impact

A cross-tenant data injection vulnerability was identified in the Snipe-IT Accessories API when Full Multiple Companies Support (FMCS) is enabled. A low-privileged authenticated user belonging to one company can create an accessory record under another company by supplying a foreign company_id value in the API request body.

The issue occurs because the API create path mass-assigns request parameters directly to the Accessory model, and the Accessory model allows company_id to be mass assigned. Unlike the web controller, which uses Company::getIdForCurrentUser() to enforce the authenticated user’s company context, the API controller does not apply equivalent tenant enforcement during accessory creation.

As a result, a Company A user can inject persistent accessory records into Company B. The injected records are then visible to Company B users as legitimate Company B inventory records. This breaks the integrity of company-scoped inventory data and represents a tenant isolation failure in the accessory creation flow.

Patches

Patched in https://github.com/grokability/snipe-it/commit/dc8cbf4786bb38b260b4ae1723ec9e7f81d82fe5

Affected versions

Packagist

PackageVulnerableFixed in
snipe/snipe-it
< 8.6.2
8.6.2

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

snipe/snipe-it Packagist → 8.6.2

composer
composer require snipe/snipe-it:^8.6.2

Severity breakdown

CVSS 3.1 8.5

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:H/A:L

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
Low

Weakness

CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')

The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.

How to prevent it
  • Requirements: Programming languages and supporting technologies might be chosen which are not subject to these issues.
  • Implementation: Utilize an appropriate mix of allowlist and denylist parsing to filter control-plane syntax from all input.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-396x-xmvh-p563
Snipe-IT: Stored XSS via Inline XML Rendering in the Uploaded Files API
Medium Also affects snipe/snipe-it
GHSA-p9h3-gvpq-5539
Snipe-IT: Stored XSS via Custom Field name in asset-list column headers
High Also affects snipe/snipe-it
GHSA-hxcx-9h4f-42xx
Snipe-IT: 2FA bypass via the API token flow
High Also affects snipe/snipe-it
GHSA-c8qc-wf67-342w
Snipe-IT: Stored DOM XSS via table selected-count IDs
Medium Also affects snipe/snipe-it
GHSA-r9r3-g9fp-3q4q
Snipe-IT: Maintenance Record Disclosure via Missing Authorization on GET
Medium Also affects snipe/snipe-it
GHSA-3hgv-jr5j-cg9x
Snipe-IT: Chained Information Disclosure and IDOR Leads to Full EULA File Takeover
Medium Also affects snipe/snipe-it
GHSA-c6w2-j4wq-mvwg
Snipe-IT: Tenant Isolation Bypass in FMCS Floater Mode
High Also affects snipe/snipe-it
GHSA-35cr-9hqq-p2mg
Snipe-IT: Cross-company deletion of pending checkout acceptances via unscoped report endpoint
Medium Also affects snipe/snipe-it
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor