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_password_manager_pro"

Found 1 matching product.

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

zohocorp / manageengine_password_manager_pro

22 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2025-11669	High	January 13, 2026 1/13/26	< 13.2 == 13.2-build13200 == 13.2-build13210 == 13.2-build13220
CVE-2024-5546	High	August 28, 2024 8/28/24	== 6.0-build6002 == 6.1-build6104 == 6.2-build6201 == 6.4-build6401 == 6.4-build6402 == 6.4-build6403 == 6.4-build6404 == 6.5-build6503 == 6.5-build6504 == 6.5-build6505 == 6.6-build6600 == 6.7-build6700 == 6.7-build6701 == 6.8-build6800 == 6.8-build6801 == 6.8-build6802 == 6.8-build6803 == 6.9-build6900 == 6.9-build6901 == 6.9-build6902 == 6.9-build6903 == 6.9-build6904 == 7.0-build7000 == 7.0-build7001 == 7.0-build7002 == 7.0-build7003 == 7.1-build7100 == 7.1-build7101 == 7.1-build7102 == 7.1-build7103 == 7.1-build7104 == 7.1-build7105 == 7.5-build7500 == 7.5-build7501 == 7.6-build7600 == 8.0-build8000 == 8.0-build8001 == 8.1-build8100 == 8.1-build8101 == 8.1-build8102 == 8.2-build8200 == 8.3-build8300 == 8.3-build8301 == 8.3-build8302 == 8.3-build8303 == 8.4-build8041 == 8.4-build8400 == 8.4-build8402 == 8.4-build8403 == 8.4-build8404 == 8.5-build8500 == 8.5-build8501 == 8.5-build8502 == 8.5-build8503 == 8.5-build8504 == 8.5-build8505 == 8.6-build8600 == 8.6-build8601 == 8.6-build8602 == 8.6-build8603 == 8.6-build8604 == 8.7-build8700 == 8.7-build8701 == 8.7-build8702 == 8.7-build8703 == 8.7-build8704 == 9.0-build9000 == 9.0-build9001 == 9.0-build9002 == 9.0-build9003 == 9.1-build9100 == 9.1-build9101 == 9.2-build9200 == 9.3-build9300 == 9.4-build9400 == 9.4-build9401 == 9.4-build9402 == 9.5-build9500 == 9.5-build9501 == 9.5-build9502 == 9.6-build9600 == 9.6-build9601 == 9.7-build9700 == 9.7-build9701 == 9.7-build9702 == 9.8-build9800 == 9.8-build9801 == 9.8-build9802 == 9.8-build9803 == 9.9-build9900 == 9.9-build9901 == 10.0-build10000 == 10.0-build10001 == 10.1-build10100 == 10.1-build10101 == 10.1-build10102 == 10.1-build10103 == 10.3-build10300 == 10.3-build10301 == 10.2-build10200 == 10.1-build10104 == 10.4-build10406 == 10.4-build10405 == 10.4-build10404 == 10.4-build10403 == 10.4-build10402 == 10.4-build10401 == 10.4-build10400 == 10.3-build10302 == 11.1-build11104 == 11.1-build11103 == 11.1-build11102 == 11.1-build11101 == 11.1-build11100 == 11.0-build11004 == 11.0-build11003 == 11.0-build11002 == 11.0-build11001 == 11.0-build11000 == 10.5-build10501 == 10.5-build10500 == 12.3-build12350 == 12.3-build12340 == 12.3-build12330 == 12.3-build12320 == 12.3-build12310 == 12.3-build12300 == 12.2-build12230 == 12.2-build12220 == 12.2-build12211 == 12.2-build12210 == 12.2-build12200 == 12.1-build12124 == 12.1-build12123 == 12.1-build12122 == 12.1-build12121 == 12.1-build12120 == 12.1-build12110 == 12.1-build12101 == 12.1-build12100 == 12.0-build12007 == 12.0-build12006 == 12.0-build12005 == 12.0-build12004 == 12.0-build12003 == 12.0-build12002 == 12.0-build12001 == 12.0-build12000 == 11.3-build11301 == 11.3-build11300 == 11.2-build11201 == 11.2-build11200 == 12.4-build12431 == 12.4-build12430 == 12.4-build12420 == 12.4-build12410 == 12.4-build12401 == 12.4-build12400
CVE-2023-6105	Medium	November 15, 2023 11/15/23	< 12.3
CVE-2020-27449	Medium	August 11, 2023 8/11/23	== 11.1-build_11101
CVE-2023-2291	High	April 26, 2023 4/26/23	*
CVE-2022-47966	Critical	January 18, 2023 1/18/23	< 12.1 == 12.1-build12100 == 12.1-build12110 == 12.1-build12120 == 12.1-build12101 == 12.1-build12121 == 12.1-build12122 == 12.1-build12123
CVE-2022-47523	Critical	January 5, 2023 1/5/23	< 12.2 == 12.2-build12200
CVE-2022-43671	Critical	November 12, 2022 11/12/22	< 12.1 == 12.1-build12100 == 12.1-build12110 == 12.1-build12120 == 12.1-build12101 == 12.1-build12121
CVE-2022-43672	Critical	November 12, 2022 11/12/22	< 12.1 == 12.1-build12100 == 12.1-build12110 == 12.1-build12120 == 12.1-build12101 == 12.1-build12121
CVE-2022-40300	Critical	September 16, 2022 9/16/22	== 5.4 == 6.3 == 5.3 == 6.4 == 6.9 == 6.0 == 6.2 == 6.5 == 5.0 == 5.1 == 5.2 == 6.1 == 6.0-build6002 == 6.1-build6104 == 6.2-build6201 == 6.4-build6401 == 6.4-build6402 == 6.4-build6403 == 6.4-build6404 == 6.5-build6503 == 6.5-build6504 == 6.5-build6505 == 6.6-build6600 == 6.7-build6700 == 6.7-build6701 == 6.8-build6800 == 6.8-build6801 == 6.8-build6802 == 6.8-build6803 == 6.9-build6900 == 6.9-build6901 == 6.9-build6902 == 6.9-build6903 == 6.9-build6904 == 7.0 == 7.0-build7000 == 7.0-build7001 == 7.0-build7002 == 7.0-build7003 == 10.4 == 10.4-build10400 == 10.4-build10402 == 10.4-build10401 == 10.3-build10301 == 10.3-build10302 == 10.3-build10300 == 10.2-build10200 == 10.1-build10101 == 10.1-build10102 == 10.1-build10103 == 10.1-build10104 == 10.1-build10100 == 10.0-build10001 == 10.0 == 11.1-build_11101 == 11.1-build_11102 == 11.1 == 11.1-build_11103 == 11.2 == 12.0-build12001 == 12.0-build12002 == 12.0-build12003 == 12.0-build12004 == 12.0-build12005 == 12.0-build12006 == 12.0-build12000 == 11.3-build11300 == 11.3-build11301 == 11.1-11104 == 12.1-build12100 == 12.1-build12110 == 12.1-build12120 == 4.6-build4600 == 4.7-build4700 == 4.8-build4803 == 7.1 == 7.1-build7100 == 7.1-build7101 == 7.1-build7102 == 7.1-build7103 == 7.1-build7104 == 7.1-build7105 == 7.5-build7500 == 7.5-build7501 == 7.6-build7600 == 8.0-build8000 == 8.0-build8001 == 8.1-build8100 == 8.1-build8101 == 8.1-build8102 == 8.2-build8200 == 8.3-build8300 == 8.3-build8301 == 8.3-build8302 == 8.3-build8303 == 8.4-build8041 == 8.4-build8400 == 8.4-build8402 == 8.4-build8403 == 8.4-build8404 == 8.5-build8500 == 8.5-build8501 == 8.5-build8502 == 8.5-build8503 == 8.5-build8504 == 8.5-build8505 == 8.6-build8600 == 8.6-build8601 == 8.6-build8602 == 8.6-build8603 == 8.6-build8604 == 8.7-build8700 == 8.7-build8701 == 8.7-build8702 == 8.7-build8703 == 8.7-build8704 == 9.0 == 9.0-build9000 == 9.0-build9001 == 9.0-build9002 == 9.0-build9003 == 9.1 == 9.1-build9100 == 9.1-build9101 == 9.2 == 9.2-build9200 == 9.3 == 9.3-build9300 == 9.4-build9400 == 9.4-build9401 == 9.4-build9402 == 9.5-build9500 == 9.5-build9501 == 9.5-build9502 == 9.6-build9600 == 9.6-build9601 == 9.7-build9700 == 9.7-build9701 == 9.7-build9702 == 9.8-build9800 == 9.8-build9801 == 9.8-build9802 == 9.8-build9803 == 9.9 == 9.9-build9900 == 9.9-build9901 == 10.0-build10000 == 12.0-build12007 == 12.1-build12101 == 11.2-build11200 == 11.2-build11201
CVE-2022-35405	Critical	July 19, 2022 7/19/22	< 12.1 == 12.1-build12100
CVE-2022-29081	Critical	April 28, 2022 4/28/22	== 10.1-build10103 == 10.1-build10104 == 10.2-build10200 == 10.3-build10300 == 10.3-build10301 == 10.3-build10302 == 10.4-build10400 == 10.4-build10401 == 10.4-build10402 == 11.1-11104 == 11.1-build_11101 == 11.1-build_11102 == 11.1-build_11103 == 11.2-build11200 == 11.2-build11201 == 11.3-build11300 == 11.3-build11301 == 12.0-build12000 == 12.0-build12001 == 12.0-build12002 == 12.0-build12003 == 12.0-build12004 == 12.0-build12005 == 12.0-build12006
CVE-2021-33617	Medium	July 31, 2021 7/31/21	== 11.2 < 11.2
CVE-2021-31857	Medium	June 16, 2021 6/16/21	== 11.1-build_11101 == 11.1-build_11102 < 11.1 == 11.1 == 11.1-build_11103
CVE-2020-9346	High	March 16, 2020 3/16/20	== 10.4 < 10.4 == 10.4-build10400 == 10.4-build10402 == 10.4-build10401
CVE-2020-9347	Critical	March 16, 2020 3/16/20	== 10.4 == 10.4-build10400 == 10.4-build10402 == 10.4-build10401 == 10.3-build10301 == 10.3-build10302 == 10.3-build10300 == 10.2-build10200 == 10.1-build10101 == 10.1-build10102 == 10.1-build10103 == 10.1-build10104 == 10.1-build10100 == 10.0-build10001 == 10.0
CVE-2016-1159	Medium	March 9, 2020 3/9/20	== 8.3-build8303 == 8.4-build8400 == 8.4-build8401 == 8.4-build8402
CVE-2019-12133	High	June 18, 2019 6/18/19	== 9.9
CVE-2017-17698	Low	December 15, 2017 12/15/17	>= 9.0 < 9.4
CVE-2015-5459	Medium	July 8, 2015 7/8/15	<= 8.1
CVE-2014-3997	High	December 5, 2014 12/5/14	== 5.0 == 5.1 == 5.2 == 5.3 == 5.4 == 6.0 == 6.0-build6002 == 6.1-build6104 == 6.2 == 6.2-build6201 == 6.3 == 6.4 == 6.4-build6401 == 6.4-build6402 == 6.4-build6403 == 6.4-build6404 == 6.5 == 6.5-build6503 == 6.5-build6504 == 6.5-build6505 == 6.6-build6600 == 6.7-build6700 == 6.7-build6701 == 6.8-build6800 == 6.8-build6801 == 6.8-build6802 == 6.8-build6803 == 6.9 == 6.9-build6900 == 6.9-build6901 == 6.9-build6902 == 6.9-build6903 == 6.9-build6904 == 7.0 == 7.0-build7000 == 7.0-build7001 == 7.0-build7002 == 7.0-build7003 == 6.1
CVE-2014-8498	Medium	November 17, 2014 11/17/14	<= 7.1

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.