Vulnerability Database

363,177

Total vulnerabilities in the database

Vulnerabilities for products matching "ws_ftp_server"

Found 2 matching products. Filters apply to all results.

You can search for specific versions with /product/ws_ftp_server/1.2.3

ipswitch / ws_ftp_server

24 vulnerabilities found
Title Severity Exploit Date Affected Version
High June 11, 2019 6/11/19
< 8.6.1
Medium June 11, 2019 6/11/19
< 8.6.1
Medium June 11, 2019 6/11/19
< 8.6.1
Medium February 2, 2007 2/2/07
== 5.04
Medium September 26, 2006 9/26/06
== 5.02
== 5.05
== 5.03
Medium September 26, 2006 9/26/06
== 5.02
== 5.03
High September 25, 2006 9/25/06
== 5.08_limited_edition
Medium September 19, 2006 9/19/06
== 5.02
== 4.01
== 3.0_1
== 1.0.1eval
== 5.03
== 1.0.2eval
Medium January 10, 2005 1/10/05
== 5.03
Medium December 31, 2004 12/31/04
== 4.01
== 3.0_1
High March 23, 2004 3/23/04
== 4.01
== 3.0_1
High September 22, 2003 9/22/03
== 4.01
Medium February 2, 1999 2/2/99
== 1.0.1eval
== 1.0.2eval

progress / ws_ftp_server

90 vulnerabilities found
Title Severity Exploit Date Affected Version
Medium August 28, 2024 8/28/24
< 8.8.8
Medium August 28, 2024 8/28/24
< 8.8.8
High February 21, 2024 2/21/24
< 8.8.5
Critical November 7, 2023 11/7/23
>= 8.8.0 < 8.8.4
< 8.7.6
Critical September 27, 2023 9/27/23
< 8.7.4
>= 8.8.0 < 8.8.2
Medium September 27, 2023 9/27/23
< 8.8.2
Medium September 27, 2023 9/27/23
< 8.8.2
High September 27, 2023 9/27/23
< 8.8.2
High September 27, 2023 9/27/23
< 8.7.4
>= 8.8 < 8.8.2
High September 27, 2023 9/27/23
< 8.7.4
>= 8.8 < 8.8.2
Critical September 27, 2023 9/27/23
< 8.7.4
>= 8.8 < 8.8.2
Medium April 3, 2023 4/3/23
== 8.6.0
High February 3, 2023 2/3/23
< 8.8
Medium June 11, 2019 6/11/19
< 8.6.1
High February 5, 2008 2/5/08
== 6.1.0.0
Medium September 26, 2006 9/26/06
== 5.0.2
Medium September 26, 2006 9/26/06
== 5.0.2
<= 5.05
Medium September 19, 2006 9/19/06
== 1.0.1
== 1.0.1.e
== 1.0.2
== 1.0.2.e
== 1.0.3
== 1.0.4
== 1.0.5
== 2.0
== 2.0.1
== 2.0.2
== 2.0.3
== 2.0.4
== 3.0
== 3.1
== 3.1.1
== 3.1.2
== 3.1.3
== 3.4
== 4.0
== 4.0.2
<= 5.05
Medium December 31, 2004 12/31/04
== 1.0.1
== 1.0.2
== 1.0.3
== 1.0.4
== 1.0.5
== 2.0
== 2.0.1
== 2.0.2
== 2.0.3
== 2.0.4
== 3.0
== 3.1
== 3.1.1
== 3.1.2
== 3.1.3
== 3.4
== 4.0
== 4.0.2
High December 31, 2004 12/31/04
== 4.0.2
High December 31, 2004 12/31/04
== 4.0.2
Medium August 29, 2004 8/29/04
== 5.0.2
High March 23, 2004 3/23/04
== 1.0.1
== 1.0.2
== 1.0.3
== 1.0.4
== 1.0.5
== 2.0
== 2.0.1
== 2.0.2
== 2.0.3
== 2.0.4
== 3.0
== 3.1
== 3.1.1
== 3.1.2
== 3.1.3
== 3.4
== 4.0
== 4.0.2
High September 22, 2003 9/22/03
== 3.4
High August 12, 2002 8/12/02
== 3.1.1
High July 26, 2001 7/26/01
== 2.0.2
Low February 2, 1999 2/2/99
== 1.0.1.e
== 1.0.2.e
Low January 2, 1999 1/2/99
== 1.0.1.e
== 1.0.2.e

Showing vulnerabilities for 2 products matching "ws_ftp_server". Each product has independent pagination.

Frequently Asked Questions

A security vulnerability is a weakness in software, hardware, or configuration that can be exploited to compromise confidentiality, integrity, or availability. Many vulnerabilities are tracked as CVEs (Common Vulnerabilities and Exposures), which provide a standardized identifier so teams can coordinate patching, mitigation, and risk assessment across tools and vendors.

CVSS (Common Vulnerability Scoring System) estimates technical severity, but it doesn't automatically equal business risk. Prioritize using context like internet exposure, affected asset criticality, known exploitation (proof-of-concept or in-the-wild), and whether compensating controls exist. A "Medium" CVSS on an exposed, production system can be more urgent than a "Critical" on an isolated, non-production host.

A vulnerability is the underlying weakness. An exploit is the method or code used to take advantage of it. A zero-day is a vulnerability that is unknown to the vendor or has no publicly available fix when attackers begin using it. In practice, risk increases sharply when exploitation becomes reliable or widespread.

Recurring findings usually come from incomplete Asset Discovery, inconsistent patch management, inherited images, and configuration drift. In modern environments, you also need to watch the software supply chain: dependencies, containers, build pipelines, and third-party services can reintroduce the same weakness even after you patch a single host. Unknown or unmanaged assets (often called Shadow IT) are a common reason the same issues resurface.

Use a simple, repeatable triage model: focus first on externally exposed assets, high-value systems (identity, VPN, email, production), vulnerabilities with known exploits, and issues that enable remote code execution or privilege escalation. Then enforce patch SLAs and track progress using consistent metrics so remediation is steady, not reactive.

SynScan combines attack surface monitoring and continuous security auditing to keep your inventory current, flag high-impact vulnerabilities early, and help you turn raw findings into a practical remediation plan.