CVE-2024-7745
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), a Missing Critical Step in Multi-Factor Authentication of the Web Transfer Module allows users to skip the second-factor verification and log in with username and password only.
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 (2022.0.8) contain a missing critical step in the Multi-Factor Authentication implementation of the Web Transfer Module. This flaw allows authenticated users to bypass the second-factor verification and gain full access using only username and password credentials, effectively circumventing the intended MFA security control.
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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Determine WS_FTP Server installed versionAccess the WS_FTP Server administrative console or use the version information command provided in the server documentation. Locate the build or version number displayed in the server status or about section.Affected if The installed version is any version prior to 8.8.8 (2022.0.8).
-
Confirm Web Transfer Module is enabledIn the WS_FTP Server administrative interface, navigate to the modules or components section and verify whether the Web Transfer Module (also referred to as the web-based transfer interface) is currently active or enabled.Affected if The Web Transfer Module is enabled and accessible to users.
-
Verify MFA configuration for Web Transfer ModuleIn the WS_FTP Server admin console, go to the security or authentication settings for the Web Transfer Module and check if Multi-Factor Authentication has been configured or enforced for user logins.Affected if MFA is configured or intended to be enforced for the Web Transfer Module, as the vulnerability allows bypassing this second-factor verification.
You are affected if your WS_FTP Server version is below 8.8.8 and the Web Transfer Module is enabled with MFA configured or intended for user authentication.
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 or later to remediate this MFA bypass vulnerability. If immediate upgrade is not feasible, consider disabling the Web Transfer Module and restricting access to FTP client connections only until the upgrade can be applied.
Ws FTP Server 8.8.8 (2022.0.8)
- 1. Identify the current version of WS_FTP Server by checking the About or version information in the management console
- 2. Download WS_FTP Server version 8.8.8 (2022.0.8) or later from the Progress customer portal or official download channel
- 3. Review the upgrade documentation provided by Progress for version 8.8.8
- 4. Perform the upgrade following the vendor's recommended upgrade procedure
- 5. After upgrade, verify that MFA is properly enforced for the Web Transfer Module
- 6. Test the authentication flow to confirm second-factor verification is now required
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-7745 — 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-7745 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