CVE-2025-5635
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 classified as critical was found in PCMan FTP Server 2.0.7. This vulnerability affects unknown code of the component PLS Command Handler. The manipulation leads to buffer overflow. The attack can be initiated 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 PLS Command Handler of PCMan FTP Server 2.0.7, allowing remote attackers to overflow a buffer and potentially execute arbitrary code. The vulnerability is exploitable remotely with a publicly disclosed exploit.
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= 2.0.7CVSS 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 PCMan FTP Server is installedCheck system for PCMan FTP Server installation. Common installation paths on Windows: C:\Program Files\PCMan FTP Server or C:\Program Files (x86)\PCMan FTP Server. Also check running processes in Task Manager for 'PCManFTP.exe' or 'PCMan FTP Server.exe'.Affected if PCMan FTP Server executable is found running or installed on the system
-
Determine the installed versionRight-click on the PCMan FTP Server executable, select Properties, then view the Details tab to see the File Version. Alternatively, check the 'About' or 'Help' menu within the application if it is running.Affected if The version number displayed is exactly 2.0.7
-
Verify the FTP service is running and exposedOpen Command Prompt and run 'netstat -an | findstr :21' to check if port 21 (FTP default port) is listening. Also check Windows Services to confirm the PCMan FTP Server service status.Affected if The FTP service is running and listening on port 21, making it network-accessible
-
Check if PLS command handler is accessibleConnect to the FTP server using an FTP client (like command-line 'ftp' or FileZilla) and attempt to send the PLS command: 'PLS'. A successful connection to the FTP server confirms the command handler is available.Affected if The FTP server accepts connections and responds to commands, indicating the PLS Command Handler is enabled and reachable
If PCMan FTP Server version 2.0.7 is installed, the FTP service is running and network-accessible, and the PLS command handler is enabled, the system is vulnerable to CVE-2025-5635.
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 dataUpdate PCMan FTP Server to a patched version if available; otherwise, consider disabling the FTP service or implementing network-level access controls to limit exposure until a patch is applied.
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5635 — 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-5635 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