CVE-2025-5330
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 vulnerability, which was classified as critical, was found in FreeFloat FTP Server 1.0. This affects an unknown part of the component RETR Command Handler. The manipulation leads to buffer overflow. It is possible to initiate the attack 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 confidenceA buffer overflow vulnerability exists in the RETR command handler of FreeFloat FTP Server 1.0. The RETR command is used to retrieve files from the FTP server, and improper bounds checking allows an attacker to overflow a buffer, potentially leading to remote code execution. With a CVSS score of 9.8 and publicly available exploits, this vulnerability is actively exploitable remotely.
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= 1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if FreeFloat FTP Server is installedCheck for FreeFloat FTP Server process running on the system. On Windows, open Task Manager and look for 'FreeFloat FTP Server.exe' or check Services panel. On command line, run: tasklist | findstr -i freefloat or Get-Process | Where-Object {$_.ProcessName -like '*freefloat*'}Affected if FreeFloat FTP Server process is running on the system
-
Confirm the installed version is 1.0Check the version of FreeFloat FTP Server. Right-click on the executable file (typically in C:\Program Files\FreeFloat or the installation directory), select Properties, and check the Version tab. Alternatively, check the About or Help menu within the FTP server applicationAffected if Version displayed is 1.0 exactly (the only affected version)
-
Verify RETR command functionality is accessibleConnect to the FTP server using any FTP client (like command-line ftp, FileZilla, or curl) and verify the RETR command is available. The RETR command is a standard FTP command and is enabled by default in FreeFloat 1.0. Run: ftp <server_ip> and attempt to log in, then use 'get' or 'retr' commandAffected if RET command is functional and accessible (this is the default state for the vulnerable server)
-
Check if FTP service is network-exposedReview firewall rules and network configuration to determine if port 21 (default FTP port) is open to external networks. Run: netsh advfirewall firewall show rule name=all | findstr FTP or check router/firewall ACLs for inbound rules allowing FTP trafficAffected if Port 21 or the configured FTP port is accessible from untrusted networks (internet or unauthorized LAN segments)
A system is affected if FreeFloat FTP Server version 1.0 is running and the RETR command is accessible, regardless of network exposure, though network exposure dramatically increases the risk of remote exploitation.
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 · scopedReplace FreeFloat FTP Server 1.0 with a modern, actively maintained FTP server solution, as FreeFloat is legacy software with no official patch. If immediate replacement is not feasible, restrict network access to the FTP service via firewall rules or ACLs to limit exposure.
- 1. Discontinue use of FreeFloat FTP Server 1.0 immediately due to critical unpatched buffer overflow vulnerability (CVE-2025-5330, CVSS 9.8).
- 2. Replace FreeFloat FTP Server with an actively maintained FTP server that receives security updates (e.g., FileZilla Server, ProFTPD, vsftpd, or Windows IIS FTP).
- 3. If replacement is not immediately feasible, restrict network access to the FTP server using firewall rules to limit exposure to trusted IP addresses only.
- 4. Disable the RETR command if possible through server configuration, though this may not fully mitigate the buffer overflow.
- 5. Monitor for any official patches or security advisories from FreeFloat, though the product appears largely unmaintained.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5330 — 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-2025-5330 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