Medium

Snipe-IT has an Open Redirect After User Edit

  • Disclosed: 28.08.2026
  • Updated: 11.10.2026 10:22

Impact

The user edit flow stores url()->previous() into Laravel's intended URL session value and later redirects with redirect()->intended(...) when redirect_option=back is submitted. Because the previous URL is derived from the attacker-controlled Referer header, an authenticated user performing a normal user-edit action can be redirected to an external attacker-controlled site.

An attacker who can cause a logged-in user with permission to edit a user record to open the edit page with an attacker-controlled Referer value.

The application can be used as a trusted redirector after a legitimate user edit action. This can support phishing or trust-boundary attacks against Snipe-IT users and matches a historical open redirect class where session-stored navigation context influences redirect destinations.

Patches

Patched in f4cac96358

Affected software

Click a technology to see all vulnerabilities affecting it.

PlatformPackageVulnerable versionsFixed in
Composer package snipe/snipe-it < 8.6.2 8.6.2

References

CVSS score 6.1/10
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
Weakness (CWE)
CWE-601
Platform
Composer
Package
snipe/snipe-it
Disclosed
28.08.2026
Updated
11.10.2026 10:22

Sources and licenses

OSV / GitHub Advisory Database - GHSA-wg2f-x2c2-c4rp - CC BY 4.0

Vulnerability history: snipe/snipe-it

All published vulnerabilities of this package (Composer package), newest first. Shows whether this is a one-off slip or a package that needs watching.

All (81) in the archive
Total entries
81
First → latest
10.2021 09.2026
Without a fix
6
Exploited in attacks
0

Severity breakdown

  • Critical 1
  • High 23
  • Medium 53
  • Low 4

Disclosures per year

  1. 2021: 10
  2. 2022: 20
  3. 2023: 2
  4. 2024: 3
  5. 2025: 6
  6. 2026: 40
Severity:
  1. High CVE-2026-63493 < 8.7.0 8.7.0
  2. High · 6.5 CVE-2026-55843 < 8.6.0 8.6.0
  3. Snipe-IT has an Open Redirect After User Edit this entry
    Medium · 6.1 CVE-2026-55461 < 8.6.2 8.6.2
  4. High · 7.1 CVE-2026-55460 < 8.6.2 8.6.2
  5. High CVE-2026-55643 < 8.6.3 8.6.3
  6. High · 8.5 CVE-2026-54329 < 8.6.2 8.6.2
  7. Critical · 9.8 CVE-2026-37709 < 8.4.1 8.4.1
  8. High · 8.8 CVE-2026-44832 < 8.4.1 8.4.1
  9. High · 8.7 CVE-2024-51093 <= 7.0.13 no fix
  10. High · 7.2 CVE-2024-48987 < 7.0.10 7.0.10
  11. High · 8.8 CVE-2023-5511 < 6.2.3 6.2.3
  12. High · 8.8 CVE-2022-23064 >= 3.0-alpha, < 5.3.8 5.3.8
  13. High · 7.4 CVE-2022-1155 >= 6.0.0-RC-1, < 6.0.0-RC-6, < 5.4.2 6.0.0-RC-6, 5.4.2
  14. High · 8.8 CVE-2022-0611 < 5.3.11 5.3.11
  15. High · 8.8 CVE-2021-4130 < 5.3.6 5.3.6
  16. High · 7.2 CVE-2021-4075 < 6.0.0-GM 6.0.0-GM
  17. High · 8.0 CVE-2021-3961 < 5.3.2 5.3.2

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application
DockRay newsletter

Application security in your inbox

Important vulnerabilities, actionable guidance and practical advice for your applications. Choose your technologies and follow what matters to your project.

  • A daily digest of new vulnerabilities, critical ones included.
  • Notifications about important updates.
  • Practical advice on application security and monitoring.

Leave empty to receive updates for every technology.

Free to subscribe. Unsubscribe with one click in any email.