CVE-2007-0665
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 · uneditedFormat string vulnerability in the SCP module in Ipswitch WS_FTP 2007 Professional might allow remote attackers to execute arbitrary commands via format string specifiers in the filename, related to the SHELL WS_FTP script command.
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 format string vulnerability exists in the SCP module of Ipswitch WS_FTP 2007 Professional that allows remote attackers to execute arbitrary commands by embedding format string specifiers (such as %n, %s, %x) in filenames when using the SHELL WS_FTP script command. The vulnerability stems from unsanitized user input being passed directly to format string functions.
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= 2007CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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.
-
Confirm WS_FTP Professional versionLocate the WS_FTP installation and check the version (typically via 'Help > About' or the executable properties). The affected version is specifically 2007.Affected if The installed version is WS_FTP Professional 2007 (any subversion).
-
Verify SCP module is in useCheck if the SCP (Secure Copy) protocol feature is enabled or configured in the WS_FTP client. Look for SCP server connections or SCP transfer profiles in the application settings.Affected if SCP module connections or profiles exist in the configuration.
-
Locate WS_FTP script filesSearch for .wsf (WS_FTP script) files on the system. These scripts may be stored in user directories, shared script folders, or the WS_FTP installation directory.Affected if WS_FTP script files (.wsf) are present on the system.
-
Inspect SHELL command usage in scriptsOpen each .wsf script file and search for the 'SHELL' command keyword. Examine whether any SHELL commands process filenames or use variables that could contain filename data.Affected if Scripts contain SHELL commands that process filenames or accept filename variables.
-
Check for untrusted filename inputReview the identified SHELL command usage to determine whether the script processes filenames from external or untrusted sources (e.g., remote server directory listings, user-supplied paths).Affected if SHELL commands in scripts can receive filenames from untrusted sources without sanitization.
You are affected if WS_FTP Professional 2007 is installed, the SCP module is used, and WS_FTP scripts contain SHELL commands that process potentially untrusted filenames.
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 to a patched version of WS_FTP Professional if available; avoid processing untrusted filenames through the SHELL command in WS_FTP scripts until the vulnerability is remediated.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0665 — 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-2007-0665 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