CVE-2025-55057: Rumpus FTP Server · CSRF
Affects Rumpus FTP ServerSource CVE Database V5
Not known to be exploited · CVSS 4.5 Medium.
Data as of 26 Oct 2026, 10:12 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 5% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:NExploitation evidence
Disclosed: evidence found.
CVE published 17 Nov 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Rumpus FTP Server | Affected
| Fixed in– |
AI-suggested
- Monitor Rumpus vendor communications closely and apply security patches immediately upon release to address CVE-2025-55057.
- Until patches are available, restrict access to the FTP server's web management interface to trusted networks and users only, using network segmentation and firewall rules.
- Enforce strong authentication and session management policies to reduce the risk of session hijacking or misuse by privileged users.
- Implement CSRF protection mechanisms such as anti-CSRF tokens and validate the origin of requests in the web interface if customization is possible.
- Conduct regular audits of FTP server configurations and logs to detect unauthorized changes promptly.
- Educate privileged users about the risks of CSRF attacks and encourage cautious behavior when interacting with web interfaces.
- Consider deploying web application firewalls (WAFs) that can detect and block suspicious CSRF-related traffic patterns.
- Limit the number of users with high privileges on the FTP server to minimize the attack surface.
- Use multi-factor authentication (MFA) for administrative access to the FTP server to add an additional security layer.
- Review and update incident response plans to include scenarios involving FTP server integrity breaches.
Description
Multiple CWE-352 Cross-Site Request Forgery (CSRF)