dbcve.org
Ftp ServerApplication · Freefloat

CVE-2025-5592

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability, which was classified as critical, has been found in FreeFloat FTP Server 1.0. Affected by this issue is some unknown functionality of the component PASSIVE Command Handler. The manipulation leads to buffer overflow. The attack may be launched remotely. The exploit has been disclosed to the public and may be used.

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 confidence

A buffer overflow vulnerability exists in the PASSIVE command handler of FreeFloat FTP Server 1.0, allowing remote attackers to potentially execute arbitrary code via specially crafted input. The vulnerability is remotely exploitable and has a public exploit available, making it easily weaponizable.

MitigationReplace FreeFloat FTP Server with a actively maintained FTP server solution (such as vsftpd, ProFTPD, or FileZilla Server) as the software is legacy and likely unmaintained. If replacement is not immediately feasible, restrict network access to the FTP service via firewall rules and implement network segmentation.

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
Ftp ServerApplication
Affected:= 1.0

CVSS 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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm FreeFloat FTP Server is running
    Check for the ftpserver.exe process in Task Manager or via command: tasklist | findstr -i ftp. Also verify port 21 is listening: netstat -an | findstr :21
    Affected if FreeFloat FTP Server process is running and port 21 is in LISTENING state
  2. Verify FreeFloat FTP Server version
    Right-click on the ftpserver.exe file, select Properties, then go to the Details tab to view the File Version. Alternatively, check the About or Help menu within the application if accessible.
    Affected if Version is 1.0 exactly (the only affected version)
  3. Confirm PASSIVE mode support is active
    Connect to the FTP server using a client and issue the PASV command to verify the server responds with a passive mode address and port. Example: ftp -n <server_ip> then quote PASV
    Affected if Server accepts and responds to the PASV command, indicating the PASSIVE handler is active
  4. Check network exposure of the FTP service
    Review firewall rules and network configuration to determine if port 21 is accessible from untrusted networks. Use: netsh advfirewall firewall show rule name=all | findstr -i ftp or review inbound rules for port 21.
    Affected if Port 21 is exposed to external/untrusted networks, making remote exploitation possible

You are affected if FreeFloat FTP Server version 1.0 is running, the PASSIVE (PASV) command is functional, and the service is network-accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace FreeFloat FTP Server with a actively maintained FTP server solution (such as vsftpd, ProFTPD, or FileZilla Server) as the software is legacy and likely unmaintained. If replacement is not immediately feasible, restrict network access to the FTP service via firewall rules and implement network segmentation.

Recommended fix High confidence
  1. This is an abandoned/end-of-life product (FreeFloat FTP Server 1.0) with no available vendor fix or patch.
  2. Discontinue use of FreeFloat FTP Server immediately due to the critical severity (CVSS 9.8) buffer overflow vulnerability.
  3. Replace with an actively maintained FTP server solution that receives security updates (e.g., vsftpd, ProFTPD, FileZilla Server, or modern alternatives).
  4. If replacement is not immediately feasible, implement network-level mitigations such as restricting access via firewall rules to limit exposure to the vulnerable service.
Caveat FreeFloat FTP Server is abandoned software with no successor version; complete replacement is required

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ftp Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-5592 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-5592 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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