CVE-2024-1474
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.5, reflected cross-site scripting issues have been identified on various user supplied inputs on the WS_FTP Server administrative interface.
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 confidenceReflected cross-site scripting (XSS) vulnerability in WS_FTP Server administrative interface allows attackers to inject malicious scripts through unsanitized user-supplied inputs, potentially compromising authenticated administrator sessions.
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.5CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 WS_FTP Server versionLocate the installed WS_FTP Server version through the administrative interface about page, installation directory metadata, or Windows Programs and Features. Compare the version number against the affected range (versions prior to 8.8.5).Affected if The installed version is below 8.8.5
-
Determine admin interface exposureVerify if the WS_FTP Server administrative web interface is network-accessible from untrusted networks. Check firewall rules, IIS bindings, or reverse proxy configurations that expose port 8080 or 443 (default admin ports).Affected if The administrative interface is accessible from external or untrusted networks without proper network segmentation
-
Review server logs for XSS patternsExamine WS_FTP Server HTTP access logs and IIS logs for suspicious request patterns containing script tags, javascript:, or other XSS vectors in URL parameters targeted at admin interface endpoints.Affected if Logs contain requests with XSS payloads directed at admin pages that may indicate exploitation attempts
The environment is affected if WS_FTP Server version is below 8.8.5 and the administrative interface is network-accessible, exposing authenticated administrators to reflected XSS attacks.
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.5
Upgrade to WS_FTP Server version 8.8.5 or later which contains the vendor patch addressing the reflected XSS issues.
8.8.5
- Download WS_FTP Server version 8.8.5 or later from the official Progress download portal
- Ensure you have a backup of your current configuration and data
- Stop the WS_FTP Server service before upgrading
- Run the installer for version 8.8.5 or later
- Follow the installation wizard prompts to complete the upgrade
- Verify the upgrade was successful by checking the version number in the administrative interface
- Restart the WS_FTP Server service
- Test the administrative interface to confirm the XSS vulnerability is resolved
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-1474 — 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-1474 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