CVE-2024-7744
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 · uneditedIn WS_FTP Server versions before 8.8.8 (2022.0.8), an Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the Web Transfer Module allows File Discovery, Probe System Files, User-Controlled Filename, Path Traversal. An authenticated file download flaw has been identified where a user can craft an API call that allows them to download a file from an arbitrary folder on the drive where that user host's root folder is located (by default this is C:)
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 confidenceWS_FTP Server versions before 8.8.8 contain a path traversal vulnerability in the Web Transfer Module. An authenticated attacker can craft malicious API calls to download files from arbitrary locations on the server's filesystem by manipulating file paths, potentially accessing system files outside the intended upload/download directory.
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< 8.8.8CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 installed WS_FTP Server versionCheck the installed version through the WS_FTP Server administration console, or use the product's built-in version check command or About dialog. Compare against the affected version range of < 8.8.8.Affected if The installed version is any release before 8.8.8 (including 8.8.7, 8.8.6, earlier 8.x releases, or older major versions).
-
Confirm Web Transfer Module is enabledAccess the WS_FTP Server administration interface and verify the Web Transfer Module service is running and accessible. This module provides the HTTP/HTTPS-based file transfer API.Affected if The Web Transfer Module service is active and accepting connections.
-
Verify API authentication is configuredCheck if user authentication is enabled for the Web Transfer Module API endpoints. Determine which user accounts have API access privileges.Affected if Authenticated users or service accounts can make API calls to the Web Transfer Module.
-
Check file operation permissionsReview the Web Transfer Module configuration to identify which directories are accessible for upload and download operations, and which users have access to those operations.Affected if Authenticated users have permission to perform file download operations through the API.
Your environment is affected if WS_FTP Server version is below 8.8.8 AND the Web Transfer Module is enabled with authenticated API access to file download operations.
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 · scoped8.8.8
Upgrade WS_FTP Server to version 8.8.8 (2022.0.8) or later. Implement strict input validation on file path parameters to prevent directory traversal sequences (../) and restrict file operations to authorized directories.
8.8.8 (2022.0.8)
- Identify the current installed version of WS_FTP Server by checking the application or using the server's version information
- Download WS_FTP Server version 8.8.8 (2022.0.8) or later from the official Progress website (www.progress.com) or authorized distribution channels
- Review the upgrade documentation and release notes for version 8.8.8
- Ensure you have a complete backup of the WS_FTP Server configuration and data
- Schedule a maintenance window for the upgrade process
- Stop the WS_FTP Server services before beginning the upgrade
- Install version 8.8.8 following the standard upgrade procedure
- Verify the installation completed successfully
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7744 — 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-2024-7744 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