dbcve.org
SftpgoApplication · Sftpgo Project

CVE-2022-39220

MEDIUM · 6.1 CVSS v3.1 Published 2022-09-20
Fix available
A fix is available. Upgrade to 2.3.5 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Cross-site scripting (XSS) vulnerability in the SFTPGo WebClient allows remote attackers to inject malicious scripts that execute in users' browsers. The vulnerability exists in all versions prior to 2.3.5 and affects the web-based client interface of the SFTP server.

MitigationUpgrade SFTPGo to version 2.3.5 or later. No workarounds are available; the web client should be restricted or monitored until the upgrade is applied.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
SftpgoApplication
Affected:< 2.3.5

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify SFTPGo installation and version
    Run 'sftpgo --version' or check the installed package version using your system package manager (e.g., 'dpkg -l sftpgo', 'rpm -qi sftpgo', or check the binary at /usr/local/bin/sftpgo --version)
    Affected if The installed version is less than 2.3.5 (e.g., 2.3.4, 2.3.0, 2.2.0, etc.)
  2. Confirm the web client interface is enabled
    Examine the SFTPGo configuration file (typically at /etc/sftpgo/sftpgo.json or ~/.sftpgo/sftpgo.json) and locate the 'httpd' section. Verify that 'bind_port' is set to a value (commonly 8080 or 8443) and 'enable_web_client' is true
    Affected if The web client is enabled and accessible on the configured port
  3. Verify web client is network accessible
    Check if the HTTP/HTTPS port configured in the httpd section is listening (e.g., run 'netstat -tlnp | grep <port>' or 'ss -tlnp | grep <port>') and attempt a local curl request: 'curl -s http://localhost:<port>/web/client/login' or test remote access if exposed
    Affected if The web client port is listening and reachable, meaning users can access the login page
  4. Review web client authentication settings
    Check the SFTPGo configuration file for authentication settings in the 'httpd' section, specifically looking at whether anonymous or unauthenticated access is permitted to the web client endpoint
    Affected if Web client is accessible without authentication or to unauthenticated users

A user is affected if SFTPGo version is below 2.3.5 AND the web client interface is enabled and accessible to users who could trigger the XSS payload.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.3.5 or later
Fixed in 2.3.5
Interim mitigation

Upgrade SFTPGo to version 2.3.5 or later. No workarounds are available; the web client should be restricted or monitored until the upgrade is applied.

Recommended fix High confidence

2.3.5

  1. 1. Review the SFTPGo 2.3.5 release notes and changelog for any configuration or behavioral changes from your current version.
  2. 2. Back up your existing SFTPGo configuration files, data directory, and any custom settings.
  3. 3. Stop the SFTPGo service.
  4. 4. Upgrade SFTPGo to version 2.3.5 using your installation method (e.g., package manager, binary replacement, or container image).
  5. 5. Restore your configuration from the backup if needed.
  6. 6. Start the SFTPGo service.
  7. 7. Verify the web client is accessible and functioning correctly.
  8. 8. Test that the XSS vulnerability is no longer present by confirming the web interface handles input properly.
Caveat No specific breaking changes mentioned in the provided material; review release notes for your specific version upgrade path

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sftpgo Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-39220 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-39220 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data