CVE-2019-12769
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 · uneditedSolarWinds Serv-U Managed File Transfer (MFT) Web client before 15.1.6 Hotfix 2 is vulnerable to Cross-Site Request Forgery in the file upload functionality via ?Command=Upload with the Dir and File parameters.
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 confidenceSolarWinds Serv-U Managed File Transfer Web client before version 15.1.6 Hotfix 2 is vulnerable to Cross-Site Request Forgery (CSRF) in the file upload functionality. The vulnerability exists in the ?Command=Upload endpoint through the Dir and File parameters, allowing attackers to trick authenticated users into unknowingly uploading malicious files.
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<= 15.1.5= 15.1.6CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Determine Serv-U MFT versionLocate the Serv-U installation and check the version number. This is typically visible in the Serv-U Administrator console, or can be found in the installation directory's version information.Affected if The installed version is 15.1.5 or earlier, OR the installed version is exactly 15.1.6 (without Hotfix 2). Compare your version against the affected ranges.
-
Verify Web client is enabledCheck if the Serv-U Web client interface is accessible. This is typically accessed via HTTP/HTTPS on the port configured during Serv-U installation (commonly ports 80, 443, or 8080).Affected if The Web client interface is enabled and reachable on your network.
-
Check for upload functionality exposureConfirm that the file upload endpoint (?Command=Upload) is present and functional in the Web client. This can be done by accessing the Web client and navigating to the upload feature, or by reviewing the web application's exposed endpoints.Affected if The upload functionality with the Dir and File parameters is exposed and accessible through the Web client.
-
Verify user authentication methodDetermine if users authenticate to the Serv-U Web client. CSRF attacks require an authenticated session to exploit the upload endpoint.Affected if Users authenticate to the Serv-U Web client interface.
You are affected if your Serv-U Managed File Transfer version is 15.1.5 or earlier, or exactly 15.1.6 without Hotfix 2, and the Web client with upload functionality is accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor hotfix 15.1.6 Hotfix 2 to remediate this vulnerability. Additionally, implement anti-CSRF tokens in the upload functionality as defense-in-depth.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-12769 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-12769 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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