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.

325,773

Total vulnerabilities in the database

Vulnerabilities for products matching "manageengine_supportcenter_plus"

Found 1 matching product.

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

zohocorp / manageengine_supportcenter_plus

31 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2025-3444	Medium	May 22, 2025 5/22/25	<= 14.8 == 14.9-14900 == 14.9-14910
CVE-2024-41150	Medium	August 23, 2024 8/23/24	== 14.8-14800 <= 14.7
CVE-2024-38869	High	August 23, 2024 8/23/24	== 14.8-14800 <= 14.7
CVE-2024-27314	Low	May 27, 2024 5/27/24	== 14.7-14710 == 14.7-14700 <= 14.6
CVE-2023-6105	Medium	November 15, 2023 11/15/23	< 14.3 == 14.3-14300 == 14.3-14301 == 14.3-14302 == 14.3-14303
CVE-2023-35785	High	August 28, 2023 8/28/23	< 14.3 == 14.3-14300
CVE-2023-38331	Medium	July 28, 2023 7/28/23	== 11.0-11000 == 11.0-11024 == 11.0-11026 == 11.0-11027 == 14.0-14000 == 14.0-14001 == 8.0-8015 == 8.1-8100 == 8.1-8101 == 8.1-8102 == 8.1-8117 == 8.1-8118 == 8.1-8119 == 8.1-8121
CVE-2023-34197	Medium	July 7, 2023 7/7/23	< 14.2 == 14.2-14200 == 14.2-14201
CVE-2023-29443	Low	April 26, 2023 4/26/23	== 14.0-14000 < 14.0 == 14.0-14001
CVE-2023-26601	High	March 6, 2023 3/6/23	== 14.0-14000 < 14.0
CVE-2023-26600	Medium	March 6, 2023 3/6/23	< 11.0 == 11.0 == 11.0-11000 == 11.0-11001 == 11.0-11002 == 11.0-11003 == 11.0-11004 == 11.0-11005 == 11.0-11006 == 11.0-11007 == 11.0-11008 == 11.0-11009 == 11.0-11010 == 11.0-11011 == 11.0-11012 == 11.0-11013 == 11.0-11014 == 11.0-11015 == 11.0-11016 == 11.0-11017 == 11.0-11018 == 11.0-11019 == 11.0-11020 == 11.0-11021 == 11.0-11022 == 11.0-11024 == 11.0-11025 == 11.0-11026 == 11.0-11027
CVE-2023-23076	Critical	February 1, 2023 2/1/23	== 11.0-11014 == 11.0-11013 == 11.0-11012 == 11.0-11011 == 11.0-11010 == 11.0-11009 == 11.0-11008 == 11.0-11007 == 11.0-11006 == 11.0-11005 == 11.0-11004 == 11.0-11003 == 11.0-11002 == 11.0-11001 == 11.0 == 11.0-11015 == 11.0-11016 == 11.0-11017 == 11.0-11018 == 11.0-11019 == 11.0-11021 == 11.0-11020 == 11.0-11022 == 11.0-11024 == 11.0-11025 == 11.0-11026 == 11.0-11027
CVE-2022-47966	Critical	January 18, 2023 1/18/23	== 11.0-11017 == 11.0-11018 == 11.0-11019 == 11.0-11021 == 11.0-11020 == 11.0-11022 == 11.0-11024 == 11.0-11025
CVE-2022-40771	Low	November 23, 2022 11/23/22	< 11.0 == 11.0 == 11.0-11000 == 11.0-11001 == 11.0-11002 == 11.0-11003 == 11.0-11004 == 11.0-11005 == 11.0-11006 == 11.0-11007 == 11.0-11008 == 11.0-11009 == 11.0-11010 == 11.0-11011 == 11.0-11012 == 11.0-11013 == 11.0-11014 == 11.0-11015 == 11.0-11016 == 11.0-11017 == 11.0-11018 == 11.0-11019 == 11.0-11020 == 11.0-11021 == 11.0-11022 == 11.0-11024 == 11.0-11025
CVE-2022-40772	Medium	November 23, 2022 11/23/22	< 11.0 == 11.0 == 11.0-11000 == 11.0-11001 == 11.0-11002 == 11.0-11003 == 11.0-11004 == 11.0-11005 == 11.0-11006 == 11.0-11007 == 11.0-11008 == 11.0-11009 == 11.0-11010 == 11.0-11011 == 11.0-11012 == 11.0-11013 == 11.0-11014 == 11.0-11015 == 11.0-11016 == 11.0-11017 == 11.0-11018 == 11.0-11019 == 11.0-11020 == 11.0-11021 == 11.0-11022 == 11.0-11024
CVE-2022-40770	High	November 23, 2022 11/23/22	< 11.0 == 11.0-11000 == 11.0-11001 == 11.0-11002 == 11.0-11003 == 11.0-11004 == 11.0-11005 == 11.0-11006 == 11.0-11007 == 11.0-11008 == 11.0-11009 == 11.0-11010 == 11.0-11011 == 11.0-11012 == 11.0-11013 == 11.0-11014 == 11.0-11015 == 11.0-11016 == 11.0-11017 == 11.0-11018 == 11.0-11019 == 11.0-11020 == 11.0-11021 == 11.0-11022 == 11.0-11024 == 11.0-11025
CVE-2022-42903	Low	November 17, 2022 11/17/22	== 11.0-11014 == 11.0-11013 == 11.0-11012 == 11.0-11011 == 11.0-11010 == 11.0-11009 == 11.0-11008 == 11.0-11007 == 11.0-11006 == 11.0-11005 == 11.0-11004 == 11.0-11003 == 11.0-11002 == 11.0-11001 == 11.0-11000 == 11.0 == 11.0-11015 == 11.0-11016 == 11.0-11017 == 11.0-11018 == 11.0-11019 == 11.0-11021 == 11.0-11020 == 11.0-11022 == 11.0-11024
CVE-2022-40773	High	November 12, 2022 11/12/22	== 11.0-11014 == 11.0-11013 == 11.0-11012 == 11.0-11011 == 11.0-11010 == 11.0-11009 == 11.0-11008 == 11.0-11007 == 11.0-11006 == 11.0-11005 == 11.0-11004 == 11.0-11003 == 11.0-11002 == 11.0-11001 == 11.0-11000 == 11.0 == 11.0-11015 == 11.0-11016 == 11.0-11017 == 11.0-11018 == 11.0-11019 < 11.0 == 11.0-11021 == 11.0-11020 == 11.0-11022 == 11.0-11024
CVE-2022-36412	Critical	July 26, 2022 7/26/22	== 11.0-11021 == 11.0-11020 == 11.0-11022
CVE-2022-35403	High	July 12, 2022 7/12/22	< 11.0 == 11.0-11000 == 11.0-11001 == 11.0-11002 == 11.0-11003 == 11.0-11004 == 11.0-11005 == 11.0-11006 == 11.0-11007 == 11.0-11008 == 11.0-11009 == 11.0-11010 == 11.0-11011 == 11.0-11012 == 11.0-11013 == 11.0-11014 == 11.0-11015 == 11.0-11016 == 11.0-11017 == 11.0-11018 == 11.0-11019 == 11.0-11020 == 11.0-11021
CVE-2022-25373	Medium	April 5, 2022 4/5/22	== 11.0-11014 == 11.0-11013 == 11.0-11012 == 11.0-11011 == 11.0-11010 == 11.0-11009 == 11.0-11008 == 11.0-11007 == 11.0-11006 == 11.0-11005 == 11.0-11004 == 11.0-11003 == 11.0-11002 == 11.0-11001 == 11.0-11000 == 11.0 == 11.0-11015 == 11.0-11016 == 11.0-11017 == 11.0-11018 == 11.0-11019 < 11.0
CVE-2021-43295	Medium	November 30, 2021 11/30/21	== 11.0-11014 == 11.0-11013 == 11.0-11012 == 11.0-11011 == 11.0-11010 == 11.0-11009 == 11.0-11008 == 11.0-11007 == 11.0-11006 == 11.0-11005 == 11.0-11004 == 11.0-11003 == 11.0-11002 == 11.0-11001 == 11.0 == 11.0-11015
CVE-2021-43296	High	November 30, 2021 11/30/21	== 11.0-11014 == 11.0-11013 == 11.0-11012 == 11.0-11011 == 11.0-11010 == 11.0-11009 == 11.0-11008 == 11.0-11007 == 11.0-11006 == 11.0-11005 == 11.0-11004 == 11.0-11003 == 11.0-11002 == 11.0-11001 == 11.0 == 11.0-11015
CVE-2021-43294	Medium	November 30, 2021 11/30/21	== 11.0-11014 == 11.0-11013 == 11.0-11012 == 11.0-11011 == 11.0-11010 == 11.0-11009 == 11.0-11008 == 11.0-11007 == 11.0-11006 == 11.0-11005 == 11.0-11004 == 11.0-11003 == 11.0-11002 == 11.0-11001 == 11.0 == 11.0-11015
CVE-2021-44077	Critical	November 29, 2021 11/29/21	< 11.0 == 11.0-11000 == 11.0-11001 == 11.0-11002 == 11.0-11003 == 11.0-11004 == 11.0-11005 == 11.0-11006 == 11.0-11007 == 11.0-11008 == 11.0-11009 == 11.0-11010 == 11.0-11011 == 11.0-11012 == 11.0-11013
CVE-2019-12133	High	June 18, 2019 6/18/19	== 8.1
CVE-2018-16965	Low	September 21, 2018 9/21/18	< 8.1
CVE-2015-5150	Low	June 30, 2015 6/30/15	== 7.90
CVE-2015-5149	Medium	June 30, 2015 6/30/15	== 7.90
CVE-2015-0866	Low	February 2, 2015 2/2/15	<= 7.9
CVE-2014-100002	Medium	January 13, 2015 1/13/15	<= 7.9

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.