CVE-2019-19659
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 · uneditedA CSRF vulnerability exists in the Web File Manager's Edit Accounts functionality of Rumpus FTP Server 8.2.9.1. By exploiting it, an attacker can take over a user account by changing the password, update users' details, and escalate privileges via RAPR/DefineUsersSet.html.
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 confidenceA CSRF vulnerability in Rumpus FTP Server 8.2.9.1's Web File Manager Edit Accounts functionality allows attackers to craft malicious requests that, when triggered by an authenticated administrator, can change passwords to take over accounts, modify user details, and escalate privileges through the RAPR/DefineUsersSet.html endpoint.
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= 8.2.9.1CVSS 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.
-
Identify installed Rumpus versionCheck the application's 'About' section in the GUI or look for version information in the installer/directory where Rumpus is installed. On Windows, this may be visible in the application window title or Help > About. On macOS, right-click the application and select Get Info.Affected if The installed version is exactly 8.2.9.1
-
Confirm Web File Manager is enabledLocate the Rumpus configuration file (rumpus.conf on Windows or ~/Library/Application Support/Rumpus/rumpus.conf on macOS) and check for the 'EnableWebFileManager' setting, or attempt to access the web interface on the configured port (default 8080).Affected if Web File Manager is enabled and accessible via HTTP/HTTPS
-
Verify DefineUsersSet.html endpoint existsAttempt to access the URL pattern 'http://[server]:[port]/RAPR/DefineUsersSet.html' in a browser or via curl. The RAPR folder contains the Web File Manager admin interface.Affected if The endpoint returns a page (200 OK), indicating the vulnerable admin interface is reachable
-
Check admin authentication stateLog into the Web File Manager as an administrator and verify session cookies are created. CSRF requires an authenticated admin session to be active when the malicious request is triggered.Affected if Administrator can log in and maintain an authenticated session in the Web File Manager
You are affected if the installed Rumpus version is exactly 8.2.9.1 AND the Web File Manager is enabled with the DefineUsersSet.html endpoint accessible to an authenticated administrator.
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 dataImplement anti-CSRF tokens or validation mechanisms on all state-changing operations in the Web File Manager, particularly the Edit Accounts and user modification functions. Additionally, validate the Origin/Referer headers and implement SameSite cookie attributes.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19659 — 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-19659 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