SFTPGo has stored XSS via inline parameter on public shares and user file download

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

3.7 · CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:L/I:L/A:N

EPSS

• CVE-2026-49245: 0.25% estimated exploitation activity in the next 30 days; percentile 16.81 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The inline query parameter on the browsable-share file download and on the authenticated user file download suppressed Content-Disposition: attachment, so an HTML file stored in a share or home directory could be served as text/html and execute in SFTPGo's web origin (stored XSS). Impact Low. Exploitation requires the attacker to place the file and a victim to open the crafted link — a URL the WebClient never generates, so it requires social engineering — and the practical conditions are narrow: - Session cookies are HttpOnly, so the cookie cannot be read by the injected script. - Authenticated shares set their own session cookie, which overwrites the victim's WebClient cookie, no account pivot. The realistic case is a public share, or a folder shared between distinct users combined with targeted social engineering. It is a genuine trust-boundary violation (SFTPGo emits attacker-controlled content as active HTML in its own origin), hence an advisory, but the constrained…

Published by the source

2 Jul 2026, 19:09 UTC

Last modified by the source

2 Jul 2026, 19:10 UTC

Source last checked

26 Oct 2026, 15:24 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-3vcg-pv95-pq54

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-49245

Advisory: SFTPGo has stored XSS via inline parameter on public shares and user file download
IDs: CVE-2026-49245, GHSA-3vcg-pv95-pq54
Record: https://patchnext.com/advisories/cve-2026-49245 (revision 1, source checked 26 Oct 2026, 15:24 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.7)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/drakkan/sftpgo/v2 2.7.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/drakkan/sftpgo/v2: affected >= 2.2.0, <= 2.7.1; fixed in 2.7.3

## Suggested inspection (read-only)
- Go github.com/drakkan/sftpgo/v2: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/drakkan/sftpgo/v2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-3vcg-pv95-pq54 (GitHub-reviewed advisory GHSA-3vcg-pv95-pq54 lists affected ranges: Go github.com/drakkan/sftpgo/v2 >=2.2.0 <=2.7.1)

Commands are suggestions: review each one before running it.