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.

346,508

Total vulnerabilities in the database

Vulnerabilities for products matching "drupal"

Found 1 matching product.

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

drupal / drupal

5778 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2007-5594	Low	October 19, 2007 10/19/07	>= 5.0 < 5.3
CVE-2007-5595	Medium	October 19, 2007 10/19/07	>= 4.7.0 < 4.7.8 >= 5.0 < 5.3
CVE-2007-5596	Low	October 19, 2007 10/19/07	>= 4.7.0 < 4.7.8 >= 5.0 < 5.3
CVE-2007-5597	Low	October 19, 2007 10/19/07	>= 4.7.0 < 4.7.8 >= 5.0 < 5.3
CVE-2007-5416	Medium	October 12, 2007 10/12/07	<= 5.2
CVE-2007-4063	Low	July 30, 2007 7/30/07	== 5.1_rev1.1 == 5.0 == 5.1
CVE-2007-4064	Low	July 30, 2007 7/30/07	== 4.7.2 == 4.7.5 == 4.7.3 == 5.0 == 4.7.0 == 4.7_rev1.15 == 4.7 == 4.7.6 == 5.1 == 4.7.4 == 4.7.1
CVE-2007-0658	Medium	February 1, 2007 2/1/07	== 4.7.2 == 4.7.5 == 4.7.3 == 5.0 == 4.7_rev1.15 == 4.7 == 4.7.6 == 5.1 == 4.7.4 == 4.7.1
CVE-2007-0626	Medium	January 31, 2007 1/31/07	>= 5.0 < 5.1 >= 4.7.0.x < 4.7.6
CVE-2007-0136	Low	January 9, 2007 1/9/07	>= 4.7.0 < 4.7.5 >= 4.6.0 < 4.6.11
CVE-2007-0124	Low	January 9, 2007 1/9/07	== 4.6.0 == 4.6 == 4.6.5 == 4.7.2 == 4.6.10 == 4.6.9 == 4.6.2 == 4.6.8 == 4.7.3 == 4.6.3 == 4.6.4 == 4.7.0 == 4.6.7 == 4.7 == 4.6.1 == 4.7.4 == 4.7.1 == 4.6.6
CVE-2006-5475	Medium	October 24, 2006 10/24/06	== 4.6.0 == 4.6.5 == 4.7.2 == 4.6.9 == 4.6.2 == 4.6.8 == 4.7.3 == 4.6.3 == 4.6.4 == 4.7.0 == 4.6.7 == 4.6.1 == 4.7.1 == 4.6.6
CVE-2006-5476	High	October 24, 2006 10/24/06	== 4.6.0 == 4.6.5 == 4.7.2 == 4.6.9 == 4.6.2 == 4.6.8 == 4.7.3 == 4.6.3 == 4.6.4 == 4.7.0 == 4.6.7 == 4.6.1 == 4.7.1 == 4.6.6
CVE-2006-5477	Low	October 24, 2006 10/24/06	== 4.6.0 == 4.6.5 == 4.7.2 == 4.6.9 == 4.6.2 == 4.6.8 == 4.7.3 == 4.6.3 == 4.6.4 == 4.7.0 == 4.6.7 == 4.6.1 == 4.7.1 == 4.6.6
CVE-2006-4120	Medium	August 14, 2006 8/14/06	<= 4.6 == 4.5.4 == 4.5.2 == 4.0 == 4.5.7 == 4.4.1 == 4.5.1 == 4.4.2 == 4.5.5 == 4.5 == 4.5.3 == 4.4.0 == 4.5.6
CVE-2006-4002	Low	August 7, 2006 8/7/06	== 4.6.0 == 4.6.5 == 4.7.2 == 4.6.2 == 4.6.8 == 4.6.3 == 4.6.4 == 4.7.0 == 4.6.7 == 4.6.1 == 4.7.1 == 4.6.6
CVE-2006-3570	Low	July 13, 2006 7/13/06	== 4.6 == 4.7
CVE-2006-2831	High	June 6, 2006 6/6/06	== 4.6.0 == 4.6 == 4.6.5 == 4.6.2 == 4.6.3 == 4.6.4 == 4.7.0 == 4.6.7 == 4.6.1 == 4.7.1 == 4.6.6
CVE-2006-2832	Low	June 6, 2006 6/6/06	== 4.6.0 == 4.6 == 4.6.5 == 4.6.2 == 4.6.3 == 4.6.4 == 4.7.0 == 4.6.7 == 4.6.1 == 4.7.1 == 4.6.6
CVE-2006-2833	Low	June 6, 2006 6/6/06	== 4.7.2 == 4.6.8
CVE-2006-2742	High	June 1, 2006 6/1/06	== 4.6.0 == 4.6 == 4.6.5 == 4.6.2 == 4.6.3 == 4.6.4 == 4.7.0 == 4.6.1 == 4.6.6
CVE-2006-2743	Medium	June 1, 2006 6/1/06	== 4.6.0 == 4.6 == 4.6.5 == 4.6.2 == 4.6.3 == 4.6.4 == 4.7.0 == 4.6.1 == 4.6.6
CVE-2006-2260	Low	May 9, 2006 5/9/06	== 4.6 == 4.5.4 == 4.5.2 == 4.6.2 == 4.5.1 == 4.6.3 == 4.5.5 == 4.5 == 4.6.1 == 4.5.3
CVE-2006-1225	Medium	March 14, 2006 3/14/06	== 4.6.0 == 4.5.0 == 4.5.2 == 4.5.1 == 4.6.1 == 4.5.3
CVE-2006-1226	Low	March 14, 2006 3/14/06	== 4.6.0 == 4.5.0 == 4.5.2 == 4.5.1 == 4.6.1 == 4.5.3
CVE-2006-1227	Low	March 14, 2006 3/14/06	== 4.6.0 == 4.6.5 == 4.5.4 == 4.5.0 == 4.5.2 == 4.6.2 == 4.5.7 == 4.5.1 == 4.6.3 == 4.6.4 == 4.5.5 == 4.6.1 == 4.5.3 == 4.5.6
CVE-2006-1228	Medium	March 14, 2006 3/14/06	== 4.6.0 == 4.5.0 == 4.5.2 == 4.5.1 == 4.6.1 == 4.5.3
CVE-2006-0070	Low	January 4, 2006 1/4/06	== 4.6.4 == 4.5.6
CVE-2005-3973	Low	December 3, 2005 12/3/05	== 4.6.0 == 4.5.4 == 4.5.0 == 4.5.2 == 4.6.2 == 4.5.1 == 4.6.3 == 4.5.5 == 4.6.1 == 4.5.3
CVE-2005-3974	Medium	December 3, 2005 12/3/05	== 4.6 == 4.5.4 == 4.5.2 == 4.6.2 == 4.5.1 == 4.6.3 == 4.5.5 == 4.5 == 4.6.1 == 4.5.3
CVE-2005-3975	Low	December 3, 2005 12/3/05	== 4.6.0 == 4.5.4 == 4.5.0 == 4.5.2 == 4.6.2 == 4.5.1 == 4.6.3 == 4.5.5 == 4.6.1 == 4.5.3
CVE-2005-1921	High	July 5, 2005 7/5/05	>= 4.6.0 < 4.6.2 < 4.5.4
CVE-2005-2106	Medium	July 5, 2005 7/5/05	== 4.6.0 == 4.5.0 == 4.5.2 == 4.5.1 == 4.6.1 == 4.5.3
CVE-2005-1871	High	June 9, 2005 6/9/05	== 4.6.0 == 4.5.0 == 4.5.2 == 4.4.1 == 4.5.1 == 4.4.2 == 4.4.0
CVE-2005-0682	Low	May 2, 2005 5/2/05	== 4.5.0 == 4.4.1 == 4.5.1 == 4.4.2 == 4.4.0
CVE-2002-1806	Low	December 31, 2002 12/31/02	== 4.0.0

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.