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

Found 1 matching product.

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

phpgroupware / phpgroupware

27 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2010-0403	Medium	May 19, 2010 5/19/10	== 0.9.16.012 <= 0.9.16.015 == 0.9.16.011 == 0.9.16.001 == 0.9.16.014 == 0.9.16.000 == 0.9.16.010 == 0.9.16.003 == 0.9.16.005 == 0.9.16.002 == 0.9.16
CVE-2010-0404	High	May 19, 2010 5/19/10	== 0.9.16.012 <= 0.9.16.015 == 0.9.16.011 == 0.9.16.001 == 0.9.16.014 == 0.9.16.000 == 0.9.16.010 == 0.9.16.003 == 0.9.16.005 == 0.9.16.002 == 0.9.16
CVE-2009-4414	Medium	December 24, 2009 12/24/09	== 0.9.16.012
CVE-2009-4415	High	December 24, 2009 12/24/09	== 0.9.16.12
CVE-2009-4416	Low	December 24, 2009 12/24/09	== 0.9.16.12
CVE-2006-4458	Medium	August 31, 2006 8/31/06	== 0.9.16.010
CVE-2005-3347	Medium	November 18, 2005 11/18/05	== 0.9.16
CVE-2005-2761	Low	August 31, 2005 8/31/05	== 0.9.16.000
CVE-2004-1383	High	December 31, 2004 12/31/04	== 0.9.14.003 == 0.9.13 == 0.9.14.005 == 0.9.14.006 == 0.9.12 == 0.9.14 == 0.9.16.000 == 0.9.16.003 == 0.9.16_rc1 == 0.9.16.002 == 0.9.14.007
CVE-2004-1384	Low	December 31, 2004 12/31/04	== 0.9.14.003 == 0.9.13 == 0.9.14.005 == 0.9.14.006 == 0.9.12 == 0.9.14 == 0.9.16.000 == 0.9.16.003 == 0.9.16_rc1 == 0.9.16.002 == 0.9.14.007
CVE-2004-1385	Medium	December 31, 2004 12/31/04	== 0.9.14.003 == 0.9.13 == 0.9.14.005 == 0.9.14.006 == 0.9.12 == 0.9.14 == 0.9.16.000 == 0.9.16.003 == 0.9.16_rc1 == 0.9.16.002 == 0.9.14.007
CVE-2004-2406	High	December 31, 2004 12/31/04	<= 0.9.14
CVE-2004-2407	High	December 31, 2004 12/31/04	<= 0.9.14
CVE-2004-2573	High	December 31, 2004 12/31/04	== 0.9.14.003 <= 0.9.14.005
CVE-2004-2574	Low	December 31, 2004 12/31/04	<= 0.9.16.005 == 0.9.16.000 == 0.9.16.003 == 0.9.16.002
CVE-2004-2575	Medium	December 31, 2004 12/31/04	== 0.9.16.000 == 0.9.16.003 == 0.9.16.005 == 0.9.16.002
CVE-2004-2576	Medium	December 31, 2004 12/31/04	== 0.9.16.000
CVE-2004-2577	Medium	December 31, 2004 12/31/04	== 0.9.16rc1 == 0.9.16rc2
CVE-2004-2578	Medium	December 31, 2004 12/31/04	== 0.9.14.003 == 0.9.1 == 0.9.2 == 0.9.7 == 0.9.13 == 0.9.14.005 == 0.9.14.006 == 0.9.9 == 0.9.3 == 0.9.12 == 0.9.16.001 == 0.9.6 == 0.9.4 == 0.9.16.000 == 0.9.5 == 0.9.10 == 0.9.8 == 0.9.9_pl1 == 0.9.14.007
CVE-2004-0875	Medium	December 23, 2004 12/23/04	== 0.9.14.003 == 0.9.13 == 0.9.14.005 == 0.9.14.006 == 0.9.12 == 0.9.16.000 == 0.9.16_rc1 == 0.9.16.002 == 0.9.14.007
CVE-2004-0016	High	February 3, 2004 2/3/04	== 0.9.14
CVE-2004-0017	High	February 3, 2004 2/3/04	== 0.9.14
CVE-2003-0599	High	August 27, 2003 8/27/03	== 0.9.16prerc <= 0.9.14.004
CVE-2003-0657	High	August 27, 2003 8/27/03	<= 0.9.14
CVE-2003-0504	Low	August 7, 2003 8/7/03	== 0.9.14.003
CVE-2002-0536	High	July 3, 2002 7/3/02	== 0.9.13
CVE-2001-0043	High	February 16, 2001 2/16/01	== 0.9.6

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.