Vulnerability Database

328,411

Total vulnerabilities in the database

Vulnerabilities for products matching "api_manager"

Found 1 matching product.

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

wso2 / api_manager

71 vulnerabilities found
Title Severity Exploit Date Affected Version
High February 24, 2026 2/24/26
>= 4.2.0 < 4.2.0.108
Critical February 19, 2026 2/19/26
== 4.2.0
== 4.3.0
== 4.4.0
== 4.5.0
== 4.6.0
Critical November 18, 2025 11/18/25
== 2.2.0
== 2.5.0
== 2.6.0
== 3.0.0
== 3.1.0
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
== 4.4.0
== 4.5.0
High November 18, 2025 11/18/25
== 3.1.0
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
== 4.4.0
== 4.5.0
== 4.6.0
Medium November 5, 2025 11/5/25
== 3.1.0
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
== 4.4.0
== 4.5.0
Medium November 5, 2025 11/5/25
== 4.2.0
== 4.3.0
== 4.4.0
== 4.5.0
High November 5, 2025 11/5/25
>= 3.1.0 < 3.1.0.345
>= 3.2.0 < 3.2.0.446
>= 3.2.1 < 3.2.1.66
>= 4.1.0 < 4.1.0.228
>= 4.2.0 < 4.2.0.169
>= 4.3.0 < 4.3.0.81
>= 4.4.0 < 4.4.0.45
>= 4.5.0 < 4.5.0.28
High November 5, 2025 11/5/25
== 3.1.0
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
== 4.4.0
== 4.5.0
Medium November 5, 2025 11/5/25
== 3.1.0
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
== 4.4.0
== 4.5.0
Medium November 5, 2025 11/5/25
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
== 4.4.0
== 4.5.0
Low October 24, 2025 10/24/25
== 3.1.0
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
== 4.4.0
== 4.5.0
Medium October 24, 2025 10/24/25
== 3.1.0
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
== 4.4.0
== 4.5.0
Critical October 16, 2025 10/16/25
== 2.0.0
== 2.1.0
== 2.2.0
== 2.5.0
== 2.6.0
== 3.0.0
== 3.1.0
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
== 4.4.0
== 4.5.0
Critical October 16, 2025 10/16/25
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
== 4.4.0
== 4.5.0
Critical October 16, 2025 10/16/25
== 2.1.0
== 2.2.0
== 2.5.0
== 2.6.0
== 3.0.0
== 3.1.0
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
== 4.4.0
== 4.5.0
Low September 23, 2025 9/23/25
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
== 4.4.0
Medium September 23, 2025 9/23/25
== 3.0.0
== 3.1.0
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
== 4.4.0
== 4.5.0
Low September 23, 2025 9/23/25
== 3.2.0
== 3.2.1
== 4.1.0
== 4.2.0
== 4.3.0
== 4.4.0
== 4.5.0
Medium September 23, 2025 9/23/25
>= 3.2.0 < 3.2.0.422
>= 3.2.1 < 3.2.1.42
>= 4.1.0 < 4.1.0.152
>= 4.3.0 < 4.3.0.55
Low June 23, 2025 6/23/25
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
Medium June 2, 2025 6/2/25
== 3.1.0
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
Low June 2, 2025 6/2/25
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
Medium June 2, 2025 6/2/25
== 3.1.0
== 3.2.0
== 4.0.0
Low May 30, 2025 5/30/25
== 2.0.0
== 2.1.0
== 2.2.0
== 2.5.0
== 2.6.0
== 3.0.0
== 3.1.0
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
Low May 30, 2025 5/30/25
== 2.1.0
== 2.2.0
== 2.5.0
== 2.6.0
== 3.0.0
== 3.1.0
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
Medium May 22, 2025 5/22/25
== 4.2.0
== 4.3.0
Critical May 22, 2025 5/22/25
== 2.2.0
== 2.5.0
== 2.6.0
== 3.0.0
== 3.1.0
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
Critical May 5, 2025 5/5/25
<= 2.0.0
Medium February 27, 2025 2/27/25
== 3.1.0
== 3.2.0
== 3.2.1
== 4.0.0
== 4.1.0
== 4.2.0
== 4.3.0
Medium February 27, 2025 2/27/25
== 4.0.0
== 4.1.0
== 4.2.0
Low December 18, 2023 12/18/23
== 2.6.0
== 3.0.0
== 2.2.0
== 3.1.0
== 3.2.0
== 2.5.0
Medium December 15, 2023 12/15/23
== 3.0.0
== 3.1.0
== 4.0.0
== 3.2.0
Medium December 15, 2023 12/15/23
== 3.1.0
== 3.2.0
Low December 15, 2023 12/15/23
<= 3.0.0
Low December 15, 2023 12/15/23
== 2.6.0
== 2.2.0
== 2.5.0
High December 15, 2023 12/15/23
>= 4.0.0 < 4.0.0.35
>= 3.2.0 < 3.2.0.86
>= 3.1.0 < 3.1.0.72
>= 3.0.0 < 3.0.0.50
>= 2.6.0 < 2.6.0.52
>= 2.5.0 < 2.5.0.32
Medium May 23, 2023 5/23/23
< 4.2.0
Critical May 11, 2022 5/11/22
== 2.6.0
== 3.0.0
== 3.1.0
== 4.0.0
== 3.2.0
Low April 21, 2022 4/21/22
== 2.6.0
== 3.0.0
== 2.2.0
== 3.1.0
== 4.0.0
== 3.2.0
== 2.5.0
Critical April 18, 2022 4/18/22
>= 2.2.0 <= 4.0.0
Medium December 7, 2021 12/7/21
== 3.0.0
== 3.1.0
== 4.0.0
== 3.2.0
Medium April 5, 2021 4/5/21
<= 3.2.0
Medium October 29, 2020 10/29/20
== 3.1.0
Medium October 21, 2020 10/21/20
<= 3.1.0
High August 27, 2020 8/27/20
== 2.2.0
Medium August 27, 2020 8/27/20
== 2.2.0
High August 27, 2020 8/27/20
<= 3.1.0
Medium August 27, 2020 8/27/20
<= 3.1.0
Critical August 21, 2020 8/21/20
<= 3.1.0
Medium August 21, 2020 8/21/20
<= 3.0.0

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.