CVE-2019-19663
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 Folder Sets Settings of Web File Manager in Rumpus FTP 8.2.9.1. This allows an attacker to Create/Delete Folders after exploiting it at RAPR/FolderSetsSet.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 · moderate confidenceA CSRF vulnerability in Rumpus FTP 8.2.9.1 Web File Manager allows authenticated administrators to be tricked into creating or deleting folders via the Folder Sets Settings page (RAPR/FolderSetsSet.html) through malicious requests from attacker-controlled sites.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Rumpus FTP versionCheck the application version through the Web File Manager login page, server status page, or by querying the running service. On Windows, check the program's Properties window. On macOS, right-click the application and select Get Info.Affected if The installed version is exactly 8.2.9.1
-
Verify Web File Manager is accessibleAttempt to access the Web File Manager interface by navigating to the server's WebDAV/RAPR URL (typically https://server:8080/ or similar port configured during setup). Confirm the login page loads.Affected if The Web File Manager interface is accessible without additional authentication beyond the admin credentials
-
Confirm administrator access to Folder Sets SettingsLog in as an administrator and navigate to the Folder Sets Settings page, typically found at RAPR/FolderSetsSet.html or through the settings menu.Affected if An authenticated administrator can access and modify folder set configurations
-
Check for anti-CSRF protection on the Folder Sets formInspect the HTML source code of the Folder Sets Settings page. Look for hidden form fields containing anti-CSRF tokens, or check if the form submission includes any token-based protection in the request headers or body.Affected if No anti-CSRF token is present in the form, and Origin/Referer header validation is not enforced on submissions
A user is affected if they are running exactly version 8.2.9.1 of Maxum Rumpus with the Web File Manager enabled and the Folder Sets Settings page lacks anti-CSRF token protection.
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 on the Folder Sets Settings form and validate Origin/Referer headers to prevent unauthorized folder creation or deletion via cross-site request forgery.
- Consultation1.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,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-19663 — 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-19663 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