Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-49245 low CVSS 3.7

Cross-Site Scripting (XSS) in github.com/drakkan/sftpgo/v2 (CVE-2026-49245)

Summary

Cross-site scripting in github.com/drakkan/sftpgo/v2 (CVE-2026-49245). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.7.3 or later.

Original description

The description as published by the source.

SFTPGo is an open source, event-driven file transfer solution. From 2.2.0 until 2.7.3, the inline query parameter on browsable-share file downloads and authenticated user-file downloads suppresses Content-Disposition: attachment, allowing an attacker-controlled HTML file stored in a share or home directory to be served as text/html in the SFTPGo web origin. An attacker who can place the file can send a crafted link to a victim, and opening that link executes the stored content in the victim's browser context. Exploitation requires social engineering and suitable share or shared-folder access, while HttpOnly session cookies limit direct cookie theft. This issue is fixed in version 2.7.3.

Source: GitHub Security Advisories (Global) NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-49245 has been found in github.com/drakkan/sftpgo/v2.
Risk of unauthorized operations or information disclosure. CVSS score: 3.7/10.
What to do: upgrade github.com/drakkan/sftpgo/v2 to 2.7.3 or later.
If unsure, ask your IT team or search "github.com/drakkan/sftpgo/v2 CVE-2026-49245" on the vendor's site.

CVE-2026-49245 (github.com/drakkan/sftpgo/v2) — CWE-79 / CVSS v3 3.7
Attack vector: remote (network-reachable)
Patched: 2.7.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in github.com/drakkan/sftpgo/v2.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/drakkan/sftpgo/v2.

🔥 Severity

Severity: Low (CVSS 3.7/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.7.3.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/drakkan/sftpgo/v2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/drakkan/sftpgo/v2' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/drakkan/sftpgo/v2 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/drakkan/sftpgo/v2 to 2.7.3

    ステージング環境で 2.7.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/drakkan/sftpgo/v2
[{"type":"SEMVER","events":[{"introduced":"2.2.0"},{"fixed":"2.7.3"}]}]
Go github.com/drakkan/sftpgo
[{"type":"SEMVER","events":[{"introduced":"0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details