# CVE-2022-39220: XSS Vulnerabilities in WebClient

> Remote attackers can inject malicious scripts into the SFTPGo web client, potentially leading to code execution or account takeover.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 20 Sep 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-cf7g-cm7q-rq7f, GO-2022-1015

## What is CVE-2022-39220?

CVE-2022-39220 is a medium-severity cross-site scripting vulnerability in drakkan sftpgo, published on 20 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

SFTPGo is an SFTP server written in Go. Versions prior to 2.3.5 are subject to Cross-site scripting (XSS) vulnerabilities in the SFTPGo WebClient, allowing remote attackers to inject malicious code. This issue is patched in version 2.3.5. No known workarounds exist.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2022-39220?

4 open source packages ship an affected version, including github.com/drakkan/sftpgo and github.com/drakkan/sftpgo/v2. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/drakkan/sftpgo` | Go | All versions | None |
| `github.com/drakkan/sftpgo` | Go | All versions | 2.3.5 |
| `github.com/drakkan/sftpgo` | Go | All versions | 2.3.5 |
| `github.com/drakkan/sftpgo/v2` | Go | All versions | 2.3.5 |

Products: Sftpgo Project Sftpgo.

## How do I fix CVE-2022-39220?

Upgrade github.com/drakkan/sftpgo to 2.3.5 or later.

## Is CVE-2022-39220 being exploited?

There is no known exploitation of CVE-2022-39220 in the wild and no public exploit code.

## Other vulnerabilities in drakkan sftpgo

- [CVE-2022-36071](https://insights.sbomify.com/CVE-2022-36071/): Recovery codes abuse in SFTPGo (high 8.3)
- [CVE-2026-30914](https://insights.sbomify.com/CVE-2026-30914/): SFTPGo has a Path Traversal and Permission Bypass via Path Normalization Discrepancy (medium 5.3)
- [CVE-2026-30915](https://insights.sbomify.com/CVE-2026-30915/): SFTPGo improperly sanitizes placeholders in group home directories/key prefixes (medium 5.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-39220 and fix it if it is affected.

What it is: CVE-2022-39220 is a medium-severity cross-site scripting vulnerability in drakkan sftpgo, published on 20 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-39220 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/drakkan/sftpgo (Go): affected all versions; no fix listed
- github.com/drakkan/sftpgo (Go): affected all versions; fixed in 2.3.5
- github.com/drakkan/sftpgo (Go): affected all versions; fixed in 2.3.5
- github.com/drakkan/sftpgo/v2 (Go): affected all versions; fixed in 2.3.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-39220/ (Markdown: https://insights.sbomify.com/CVE-2022-39220/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-39220
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-39220
- OSV: https://osv.dev/vulnerability/CVE-2022-39220

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-39220/
Summaries are generated and may contain mistakes; the official description above is the record.