CVE-2022-39187
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 · uneditedRumpus - FTP server version 9.0.7.1 has a Reflected cross-site scripting (RXSS) vulnerability through unspecified vectors.
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 confidenceRumpus FTP server version 9.0.7.1 contains a reflected cross-site scripting (RXSS) vulnerability in its web interface. Attackers can inject malicious scripts through unspecified vectors, which are then reflected back to victim users. This allows session hijacking, credential theft, or defacement of the web interface.
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<= 9.0.7.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Rumpus FTP server versionCheck the installed version of Maxum Rumpus FTP server. This can typically be found in the application itself (Help > About), the installer file properties, or by querying the running service if accessible.Affected if The installed version is 9.0.7.1 or any version lower than 9.0.7.1 (any version <= 9.0.7.1).
-
Verify web interface is enabledConfirm that the Rumpus web interface is enabled and accessible. This is typically accessed via HTTP/HTTPS on a configured port (default often 8080 or 2000). Check the Rumpus server configuration for web interface settings.Affected if The web interface is enabled and exposed to users or network attackers.
-
Check for active web sessionsInspect whether users are actively using or likely to use the web interface for file transfers or administration. Review server logs for web interface access patterns.Affected if Users access the web interface, as RXSS requires victim interaction to execute malicious scripts.
A user is affected if they run Maxum Rumpus version 9.0.7.1 or lower AND have the web interface enabled, as this provides the attack surface for reflected XSS injection.
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 input validation and output encoding across all user-supplied parameters in the web interface. Deploy Content Security Policy (CSP) headers and ensure the web application uses HttpOnly and Secure flags for session cookies.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39187 — 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-2022-39187 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