CVE-2026-86760

snipe-it 8.2.0 before 8.7.0 Authentication Bypass via activated flag

Published Sep 9, 2026 CVSS 4.0 · 5.3 Medium EPSS < 1% KEV · Not listed
Description
Snipe-IT versions 8.2.0 through 8.6.x (fixed in 8.7.0) contain an incorrect authorization flaw in app/Http/Controllers/Users/UsersController::update(). The single-user edit route assigned the activated field from the request payload before evaluating the canEditAuthFields authorization gate, so an authenticated non-admin user holding the users.edit permission in the target's company scope can submit a full valid PUT request to /users/{id} and toggle the activated flag on any user, including admin and superuser accounts. Deactivating an admin locks that account out of the application until another admin or superuser re-enables it. Only the activated field is affected; username, email, password and permissions remain protected by the gate, no data is disclosed, and the API (Api\UsersController::update) and bulk-edit paths are not affected.

Analysis

AI-generated

Technical impact

An incorrect authorization logic in the user update controller allows an authenticated user who holds the users.edit permission within the same company scope to toggle the activated flag on any user account, including administrators and superusers. The vulnerability affects only the activated attribute; name, email, password, and permission data remain protected, and no external data exposure occurs. The ability to deactivate an admin account effectively locks that account out of the application until another privileged user re‑enables it.

Affected Systems

The vulnerability affects Snipe-IT versions 8.2.0 through 8.6.x, prior to the 8.7.0 release, as distributed by Snipe‑IT App. The affected versions are 8.2.0–8.6.x. The flaw resides in the UsersController::update endpoint; bulk‑edit paths are not impacted.

Risk and Exploitability

The CVSS score is 5.3, indicating medium severity. EPSS is not available, and the vulnerability is not listed in CISA’s KEV catalog. The attack vector requires an authenticated session with the users.edit permission within the target company. While no data is disclosed or code executed, the attacker can toggle any user’s activation status, potentially locking out administrators or superusers until another privileged user re-enables the account. The overall risk is moderate due to the potential account lockout and the need for privileged permissions.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Snipe‑IT to version 8.7.0 or later to apply the vendor’s fix.
  • Restrict the users.edit permission to administrator and superuser roles only, preventing non‑admin users from modifying activation status.
  • Audit current user roles and disabled accounts to identify any unauthorized admin deactivations and restore access as needed.
  • Configure alerting for future account deactivations to detect potential misuse promptly.

Generated by OpenCVE AI on September 9, 2026 at 16:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Grokability
Grokability snipe-it
Vendors & Products Grokability
Grokability snipe-it
Type Values Removed Values Added
Description Snipe-IT versions 8.2.0 through 8.6.x (fixed in 8.7.0) contain an incorrect authorization flaw in app/Http/Controllers/Users/UsersController::update(). The single-user edit route assigned the activated field from the request payload before evaluating the canEditAuthFields authorization gate, so an authenticated non-admin user holding the users.edit permission in the target's company scope can submit a full valid PUT request to /users/{id} and toggle the activated flag on any user, including admin and superuser accounts. Deactivating an admin locks that account out of the application until another admin or superuser re-enables it. Only the activated field is affected; username, email, password and permissions remain protected by the gate, no data is disclosed, and the API (Api\UsersController::update) and bulk-edit paths are not affected.
Title snipe-it 8.2.0 before 8.7.0 Authentication Bypass via activated flag
First Time appeared Snipeitapp
Snipeitapp snipe-it
Weaknesses CWE-863
CPEs cpe:2.3:a:snipeitapp:snipe-it:*:*:*:*:*:*:*:*
Vendors & Products Snipeitapp
Snipeitapp snipe-it
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L'}

cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N'}

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Sep 14, 2026, 1:28 PM
Reserved
Sep 8, 2026, 11:33 AM
Status
Analyzed
Published
Sep 9, 2026, 2:17 PM
Modified
Sep 16, 2026, 8:26 PM