How should we interpret CVSS severity scores?

CVSS estimates technical severity, but it does not automatically equal business risk. Prioritize using context like internet exposure, asset criticality, known exploitation, 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.

Vulnerability Database

Q: What is a Vulnerability (CVE) and why does it matter?

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.

Q: What's the difference between a vulnerability, an exploit, and a zero-day?

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. Risk increases sharply when exploitation becomes reliable or widespread.

Q: Why do vulnerabilities keep reappearing in our environment?

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.

Q: How do we prioritize remediation without burning out the team?

Use a 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 so remediation is steady, not reactive.

Q: How can SynScan help reduce vulnerability risk over time?

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.

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "unified_communications_manager"

Found 1 matching product.

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

cisco / unified_communications_manager

235 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2026-20045	High	January 21, 2026 1/21/26	>= 12.5 < 14su5 >= 15.0 <= 15su3a
CVE-2025-20326	Low	September 3, 2025 9/3/25	>= 15.0 < 15su3 == 12.5 == 14.0
CVE-2025-20309	Critical	July 2, 2025 7/2/25	== 15.0.1.13010-1 == 15.0.1.13011-1 == 15.0.1.13012-1 == 15.0.1.13013-1 == 15.0.1.13014-1 == 15.0.1.13015-1 == 15.0.1.13016-1 == 15.0.1.13017-1
CVE-2025-20278	Medium	June 4, 2025 6/4/25	== 12.5(1) == 12.5(1)su7 == 12.5(1)su2 == 12.5(1)su4 == 12.5(1)su3 == 12.5(1)su5 == 12.5(1)su1 == 12.5(1)su6 == 12.5(1)su7a == 12.5(1)su8 == 12.5(1)su8a == 12.5(1)su9
CVE-2020-3420	Unknown	November 18, 2024 11/18/24	*
CVE-2024-20511	Medium	November 6, 2024 11/6/24	== 12.5(1) == 12.5(1)su7 == 12.5(1)su2 == 12.5(1)su4 == 12.5(1)su3 == 12.5(1)su5 == 12.0(1)su2 == 12.0(1)su3 == 12.5(1)su1 == 12.0(1)su1 == 12.0(1)su4 == 12.0(1)su5 == 12.5(1)su6 == 12.5(1)su7a == 12.5(1)su8 == 12.5(1)su8a == 12.5(1)su9
CVE-2024-20488	Medium	August 21, 2024 8/21/24	== 12.5(1) == 14.0 == 12.5(1)su7 == 12.5(1)su2 == 12.5(1)su4 == 12.5(1)su3 == 12.5(1)su5 == 12.5(1)su6 == 12.5(1)su7a == 12.5(1)su8 == 12.5(1)su8a == 12.5(1)su9 == 14.0su1 == 14.0su2 == 14.0su3 == 14.0su4 == 14.0su4a == 15.0 == 12.5(1)su1 == 14.0su2a == 12.6(1)
CVE-2024-20375	High	August 21, 2024 8/21/24	== 12.5(1) == 12.5(1)su7 == 12.5(1)su2 == 12.5(1)su4 == 12.5(1)su3 == 12.5(1)su5 == 12.0(1)su1 == 12.0(1)su2 == 12.0(1)su3 == 12.0(1)su4 == 12.0(1)su5 == 12.5(1)su1 == 12.5(1)su6 == 12.5(1)su7a == 12.5(1)su8 == 12.5(1)su8a
CVE-2024-20253	Critical	January 26, 2024 1/26/24	< 12.5\(1\)su8 >= 14.0 < 14su3
CVE-2023-20259	High	October 4, 2023 10/4/23	== 12.5(1)su7 == 14su3
CVE-2023-20266	Medium	August 30, 2023 8/30/23	== 12.5.1su8
CVE-2023-20211	High	August 16, 2023 8/16/23	== 14.0 >= 12.5\(1\) < 12.5\(1\)sub
CVE-2023-20242	Low	August 16, 2023 8/16/23	== 11.5(1) == 12.5(1) == 14.0
CVE-2023-20116	Medium	June 28, 2023 6/28/23	== 11.5(1.10000.6) == 12.0(1.10000.10) == 12.5(1.10000.22) == 14.0(1.10000.20)
CVE-2023-20010	High	January 20, 2023 1/20/23	>= 14.0 < 14su2 >= 11.5\(1\) < 12.5\(1\)su7 < 12.5\(1\)su7
CVE-2022-20816	Medium	August 10, 2022 8/10/22	>= 11.5\(1\) < 14su2
CVE-2022-20752	Medium	July 6, 2022 7/6/22	>= 12.5\(1\) < 12.5\(1\)su6 >= 14.0 < 14su1
CVE-2022-20791	Medium	July 6, 2022 7/6/22	<= 11.5\(1.10000.6\) >= 12.5 <= 12.5\(1.10000.22\) >= 14.0 <= 14.0\(1.10000.20\)
CVE-2022-20800	Medium	July 6, 2022 7/6/22	>= 11.5\(1\) < 14su2
CVE-2022-20815	Medium	July 6, 2022 7/6/22	>= 14.0 < 14su2
CVE-2022-20859	Medium	July 6, 2022 7/6/22	>= 14.0 < 14su2
CVE-2022-20862	Low	July 6, 2022 7/6/22	< 12.5\(1\)su6 >= 14.0 < 14su2
CVE-2022-20787	Medium	April 21, 2022 4/21/22	>= 14.0 < 14su1 >= 12.5\(1\) < 12.5\(1\)su6
CVE-2022-20788	Medium	April 21, 2022 4/21/22	>= 11.5\(1\) < 11.5\(1\)su11 >= 12.5\(1\) < 12.5\(1\)su6 >= 14.0 < 14su1
CVE-2022-20789	Low	April 21, 2022 4/21/22	== 12.5(1) == 14.0
CVE-2022-20790	Medium	April 21, 2022 4/21/22	<= 14.0
CVE-2022-20804	Medium	April 21, 2022 4/21/22	<= 14.0
CVE-2021-44228	Critical	December 10, 2021 12/10/21	< 11.5\(1\) == 11.5(1)su3 == 11.5(1) == 11.5(1.22900.28) == 11.5(1.21900.40) == 11.5(1.18900.97) == 11.5(1.18119.2) == 11.5(1.17900.52)
CVE-2021-34701	Low	November 4, 2021 11/4/21	< 14su1
CVE-2021-34773	Medium	November 4, 2021 11/4/21	== 14.0(1.10000.20)
CVE-2021-1478	Medium	May 6, 2021 5/6/21	< 12.6
CVE-2021-1362	High	April 8, 2021 4/8/21	>= 10.5\(2\) < 11.5\(1\)su9 >= 12.0\(1\) < 12.5\(1\)su4
CVE-2021-1380	Medium	April 8, 2021 4/8/21	< 14
CVE-2021-1399	Low	April 8, 2021 4/8/21	>= 10.5\(2\) < 12.5\(1\)su4
CVE-2021-1406	Low	April 8, 2021 4/8/21	== 12.5(1) == 12.0(1) == 10.5(2) == 11.5(1) == 10.5(2)su1 == 10.5(2)su2 == 10.5(2)su2a == 10.5(2)su3 == 10.5(2)su3a == 10.5(2)su4 == 10.5(2)su4a == 10.5(2)su5 == 10.5(2)su6 == 10.5(2)su6a == 10.5(2)su7 == 10.5(2)su8 == 10.5(2)su9 == 10.5(2)su10 == 12.5(1)su1 == 12.5(1)su2 == 12.5(1)su3 == 12.5(1)su4 == 12.5(1)su5 == 11.5(1)su1 == 11.5(1)su2 == 11.5(1)su3 == 11.5(1)su4 == 11.5(1)su5 == 11.5(1)su7 == 11.5(1)su8 == 11.5(1)su9
CVE-2021-1407	Medium	April 8, 2021 4/8/21	< 14
CVE-2021-1408	Medium	April 8, 2021 4/8/21	< 14
CVE-2021-1409	Medium	April 8, 2021 4/8/21	< 14
CVE-2021-1355	Medium	January 20, 2021 1/20/21	< 11.5\(1\)su9 >= 12.0 < 12.0\(1\)su4 >= 12.5 < 12.5\(1\)su4
CVE-2021-1357	Medium	January 20, 2021 1/20/21	< 11.5\(1\)su9 >= 12.0 < 12.0\(1\)su4 >= 12.5 < 12.5\(1\)su4
CVE-2021-1364	Medium	January 20, 2021 1/20/21	< 11.5\(1\)su9 >= 12.0 < 12.0\(1\)su4 >= 12.5 < 12.5\(1\)su4
CVE-2021-1282	Medium	January 20, 2021 1/20/21	< 11.5\(1\)su9 >= 12.0 < 12.0\(1\)su4 >= 12.5 < 12.5\(1\)su4
CVE-2021-1226	Low	January 13, 2021 1/13/21	== 10.5(2) >= 11.5\(1\) < 11.5\(1\)su9
CVE-2020-3135	High	September 23, 2020 9/23/20	< 11.5\(1\)
CVE-2019-15963	Medium	September 23, 2020 9/23/20	>= 12.5 <= 12.5\(1.10000.22\) >= 12.0 <= 12.0\(1.10000.10\) >= 11.5 <= 11.5\(1.10000.6\) >= 10.5 <= 10.5\(2.10000.5\)
CVE-2020-3346	Medium	August 17, 2020 8/17/20	== 12.5(1) == 12.0(1) >= 11.5\(1\) <= 11.5\(1\)su8 >= 10.5\(2\) <= 10.5\(2\)su10
CVE-2020-3282	Medium	July 2, 2020 7/2/20	>= 10.5\(2\) < 10.5\(2\)su10 >= 11.5\(1\) < 11.5\(1\)su8 == 12.0(1) == 12.5(1)
CVE-2020-3177	High	April 15, 2020 4/15/20	== 10.5(2.10000.5) == 11.5(1.10000.6) == 12.0(1.10000.10) == 12.5(1.10000.22)
CVE-2015-0749	Low	February 19, 2020 2/19/20	<= 10.5\(2.10000.5\)
CVE-2019-15972	High	November 26, 2019 11/26/19	== 11.5(1.10000.6) == 10.5(2.10000.5) == 12.0(1.10000.10) == 12.5(1.10000.22)

Deep Security Visibility Without the Complexity

SynScan provides clear, real-time security insights so you can monitor your attack surface, spot risks early, and act fast—without extra complexity.

No setup fees
5-min deployment
Cancel anytime

Book a Demo

Frequently Asked Questions

What is a Vulnerability (CVE) and why does it matter?

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.