CVE-2022-46369
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 Persistent cross-site scripting (PXSS) – vulnerability may allow inserting scripts into unspecified input fields.
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 persistent cross-site scripting (PXSS) vulnerability where malicious scripts can be injected into unspecified input fields and stored on the server, potentially executing in the browsers of users who access the affected functionality.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 the installed Rumpus versionOpen the Rumpus application and navigate to Help > About, or check the application bundle info. On Windows, right-click the executable and view Properties > Details. On macOS, right-click the app > Get Info.Affected if Version displayed is 9.0.7.1 or lower
-
Confirm version against CVE scopeCompare your installed version number to the affected range: any version of Maxum Rumpus FTP server at or below 9.0.7.1 is within scope.Affected if Installed version is <= 9.0.7.1 (exact match or lower)
-
Identify user input fields in the web interfaceLog into the Rumpus web administration interface and enumerate all fields that accept and store user data, such as user accounts, custom messages, file descriptions, or share names.Affected if The application stores any user-supplied input that gets rendered back to users without sanitization
You are affected if the installed Rumpus version is 9.0.7.1 or lower and the application stores user-supplied input in any field that gets displayed to other 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.
dbcve · scopedImplement input validation and output encoding on all user-supplied input fields, apply Content Security Policy headers, and contact the vendor for a patched version if available.
Rumpus version 9.0.8 or later (verify latest stable release)
- 1. Backup your current Rumpus configuration and data
- 2. Download the latest version of Rumpus FTP server from the official vendor website (https://www.kx.com/)
- 3. Review the release notes for version 9.0.8 or later for security updates
- 4. Install the new version following the vendor's upgrade instructions
- 5. Verify the XSS vulnerability is remediated by testing the previously affected input fields
- 6. Confirm normal server functionality after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing3.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46369 — 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-46369 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