CVE-2025-5636
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, has been found in PCMan FTP Server 2.0.7. This issue affects some unknown processing of the component SET Command Handler. The manipulation leads to buffer overflow. The attack may 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 · high confidenceA buffer overflow vulnerability exists in PCMan FTP Server 2.0.7 within the SET command handler component. The vulnerability allows remote attackers to overflow a buffer during SET command processing, potentially enabling arbitrary code execution or denial of service. The exploit is publicly available, increasing exploitation risk.
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 for the PCMan FTP Server executable (pcmanftpd.exe or PCManFTPD.exe) in common installation paths such as C:\Program Files\PCMan FTP Server or C:\Program Files (x86)\PCMan FTP Server. Also check running processes in Task Manager for pcmanftpd.exe or similar FTP server processes.Affected if PCMan FTP Server executable is found on the system
-
Determine the installed versionRight-click the PCMan FTP Server executable, select Properties, and check the Version tab for the product version. Alternatively, connect to the FTP server with any client and issue the 'STAT' or 'VERSION' command if supported, or check the application's Help > About dialog.Affected if The version is 2.0.7 or lower, or if the version cannot be determined but the application is present
-
Verify the FTP service is accessibleConfirm the PCMan FTP Server service is running and listening on the configured port (typically port 21). Use netstat -an | findstr :21 or check services.msc to verify the service status.Affected if The FTP server is running and accepting connections
-
Confirm SET command functionality is availableConnect to the FTP server using any FTP client and issue the 'SET' command with a test parameter (e.g., 'SET test'). In the vulnerable version, this command handler is present and will process the input.Affected if The SET command is recognized and processes without returning an error indicating the feature is unavailable
If PCMan FTP Server version 2.0.7 or lower is installed and running with the SET command available, the system is affected by this vulnerability.
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 dataUpgrade to a patched version of PCMan FTP Server if available, or migrate to a maintained FTP server solution. If continued use is required, implement network-level access controls to limit exposure and consider deploying a WAF to filter malicious SET command payloads.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5636 — 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-5636 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