Description
Snipe-IT versions 4.2.0 through 8.6.3 expose Laravel Passport's auto-registered personal-access-token routes (GET, POST, DELETE /oauth/personal-access-tokens*) with only 'web' and 'auth:web' middleware, without the self.api permission gate that Snipe-IT enforces on its own token endpoints (/account/api and /api/v1/account/personal-access-tokens). Any user with a valid web session and the corresponding CSRF token can POST to /oauth/personal-access-tokens and mint a long-lived bearer token for their own account, even when an administrator has denied the self.api permission. The issued token is still subject to existing per-endpoint authorization policies, so this is not a privilege escalation; it defeats the administrative control intended to block API/scripted access at the user's own permission level. Fixed in 8.7.0 (commit 3f74b8c), which registers overriding routes wrapped in the can:self.api middleware.
Affected products
| Vendor | Product | Affected | Fixed |
|---|---|---|---|
| grokability | snipe-it | 4.2.0 – ≤ 8.7.2 | — |
Advisories 1
- WID-SEC-2026-2981 Snipe-IT: Mehrere Schwachstellen BSI CERT-Bund (WID) · Sep 24, 2026
References
- GitHub Security Advisory (GHSA-76pf-qf59-ff3q) vendor-advisory
- VulnCheck Advisory: Snipe-IT 4.2.0 through 8.6.3 Permission Bypass via OAuth third-party-advisory