Skip to content

Open redirect vulnerability (v8.4.0)

Moderate
snipe published GHSA-mghp-5cq4-v6mg May 5, 2026

Package

No package listed

Affected versions

<8.4.1

Patched versions

8.4.1

Description

Open redirect vulnerability in Snipe-IT allows attackers to redirect users to malicious sites via unvalidated HTTP Referer header stored in session variable.

Impact

  • Phishing: Redirect users to fake login pages to steal credentials
  • Session Hijacking: Redirect to attacker site that captures session cookies via JavaScript
  • Malware Distribution: Redirect to sites hosting malware or drive-by downloads
  • Reputation Damage: Users lose trust when redirected to malicious sites from legitimate application
  • Social Engineering: Use trusted Snipe-IT domain to increase phishing success rate

When the user clicks "Save", the application:

  1. Processes the form
  2. Checks redirect_option (if set to 'back')
  3. Calls Helper::getRedirectOption()
  4. Retrieves back_url from session: https://evil.com/phishing?target=snipeit
  5. Executes redirect()->to($backUrl)
  6. User is redirected to attacker's site

This would still require session poisoning, so the actual practical threat here is minimal.

Patches

Patched in e376492, released in 8.4.1

Workarounds

None

References

  • CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
  • OWASP: Unvalidated Redirects and Forwards
  • Laravel Security: Safe Redirects

snipeit_open_redirect_submission.md

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Adjacent
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:A/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

CVE ID

CVE-2026-44833

Weaknesses

No CWEs

Credits