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.

327,594

Total vulnerabilities in the database

Vulnerabilities for products matching "groupware"

Found 4 matching products. Filters apply to all results.

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

horde / groupware

46 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2025-41066	Medium	December 2, 2025 12/2/25	== 5.2.22
CVE-2022-30287	High	July 28, 2022 7/28/22	<= 5.2.22
CVE-2021-26929	Medium	February 14, 2021 2/14/21	<= 5.2.22
CVE-2020-8034	Medium	May 18, 2020 5/18/20	== 5.2.22
CVE-2020-8035	Medium	May 18, 2020 5/18/20	< 5.2.22
CVE-2020-8865	Medium	March 23, 2020 3/23/20	== 5.2.22
CVE-2020-8866	Medium	March 23, 2020 3/23/20	== 5.2.22
CVE-2020-8518	Critical	February 17, 2020 2/17/20	== 5.2.22
CVE-2013-6275	Medium	November 5, 2019 11/5/19	<= 5.1.2
CVE-2013-6364	High	November 5, 2019 11/5/19	== 5.1.2
CVE-2013-6365	Medium	November 5, 2019 11/5/19	== 5.1.2
CVE-2019-12095	High	October 24, 2019 10/24/19	<= 5.2.22
CVE-2019-12094	Medium	October 24, 2019 10/24/19	<= 5.2.22
CVE-2019-9858	High	May 29, 2019 5/29/19	== 5.2.17 == 5.2.22
CVE-2017-16906	Low	November 20, 2017 11/20/17	>= 5.2.19 <= 5.2.22
CVE-2017-16907	Low	November 20, 2017 11/20/17	== 5.2.21 == 5.2.19
CVE-2017-16908	Low	November 20, 2017 11/20/17	== 5.2.19
CVE-2017-15235	Medium	October 11, 2017 10/11/17	== 5.2.21
CVE-2017-7413	High	April 4, 2017 4/4/17	<= 5.2.17
CVE-2017-7414	Medium	April 4, 2017 4/4/17	== 5.0.2 == 5.1.5 == 5.1.1 == 5.0.0-rc1 == 5.1.0 == 5.2.0-rc1 == 5.2.1 == 5.2.5 == 5.2.2 == 5.0.5 == 5.1.3 == 5.0.0 == 5.1.2 == 5.2.3 == 5.2.0 == 5.1.4 == 5.1.0-rc1 == 5.2.4 == 5.0.4 == 5.0.3 == 5.2.6 == 5.0.1 == 5.2.7
CVE-2016-5303	Low	December 20, 2016 12/20/16	== 5.2.15
CVE-2016-2228	Low	April 13, 2016 4/13/16	<= 5.2.11
CVE-2015-8807	Low	April 13, 2016 4/13/16	== 5.2.11
CVE-2015-7984	Medium	November 19, 2015 11/19/15	>= 5.0.0 < 5.2.11
CVE-2014-4945	Low	July 14, 2014 7/14/14	<= 5.1.4 == 5.0.0 == 5.0.0-rc1 == 5.0.1 == 5.0.2 == 5.0.3 == 5.0.4 == 5.0.5 == 5.1.0 == 5.1.0-rc1 == 5.1.1 == 5.1.2 == 5.1.3
CVE-2014-4946	Low	July 14, 2014 7/14/14	<= 5.1.4 == 5.0.0 == 5.0.0-rc1 == 5.0.1 == 5.0.2 == 5.0.3 == 5.0.4 == 5.0.5 == 5.1.0 == 5.1.0-rc1 == 5.1.1 == 5.1.2 == 5.1.3
CVE-2012-5565	Low	April 5, 2014 4/5/14	== 4.0 == 4.0.3 == 4.0-rc1 == 4.0.2 == 4.0.7 == 4.0.1 == 4.0.5 <= 4.0.8 == 4.0-rc2 == 4.0.4 == 4.0.6
CVE-2012-5566	Low	April 5, 2014 4/5/14	== 4.0 == 4.0.3 == 4.0-rc1 == 4.0.2 == 4.0.1 == 4.0.5 <= 4.0.7 == 4.0-rc2 == 4.0.4 == 4.0.6
CVE-2012-5567	Low	April 5, 2014 4/5/14	== 4.0 == 4.0.3 == 4.0-rc1 == 4.0.2 == 4.0.7 == 4.0.1 == 4.0.5 <= 4.0.8 == 4.0-rc2 == 4.0.4 == 4.0.6
CVE-2012-6640	Low	April 5, 2014 4/5/14	== 4.0 == 4.0.3 == 4.0-rc1 == 4.0.2 == 4.0.7 == 4.0.1 == 4.0.5 <= 4.0.8 == 4.0-rc2 == 4.0.4 == 4.0.6
CVE-2012-0209	High	September 25, 2012 9/25/12	== 1.2.10
CVE-2010-3693	Low	April 4, 2011 4/4/11	== 1.1 == 1.0 == 1.2.2 == 1.1.5 == 1.2.1 == 1.0.2 == 1.0.1 == 1.0.5 == 1.1.1 == 1.0.3 == 1.1.3 == 1.0.4 == 1.2-rc1 == 1.2 == 1.1.4 == 1.1.2 == 1.2.3 == 1.0-rc1 == 1.0-rc2 == 1.0.6 == 1.0.7 == 1.0.8 == 1.1-rc1 == 1.1-rc2 == 1.1-rc3 == 1.1-rc4 == 1.1.6 == 1.2.4 == 1.2.5 <= 1.2.6 == 1.2.3-rc1
CVE-2010-4778	Low	April 4, 2011 4/4/11	== 1.1 == 1.0 == 1.2.2 == 1.1.5 == 1.2.1 == 1.0.2 == 1.0.1 == 1.0.5 == 1.1.1 == 1.0.3 == 1.1.3 == 1.0.4 == 1.2-rc1 == 1.2 == 1.1.4 == 1.1.2 == 1.2.3 == 1.0-rc1 == 1.0-rc2 == 1.0.6 == 1.0.7 == 1.0.8 == 1.1-rc1 == 1.1-rc2 == 1.1-rc3 == 1.1-rc4 == 1.1.6 == 1.2.4 == 1.2.5 <= 1.2.6 == 1.2.3-rc1
CVE-2010-3695	Low	March 31, 2011 3/31/11	== 1.1 == 1.0 == 1.2.2 == 1.1.5 == 1.2.1 == 1.0.2 == 1.0.1 == 1.0.5 == 1.1.1 == 1.0.3 == 1.1.3 == 1.0.4 == 1.2-rc1 == 1.2 == 1.1.4 == 1.1.2 == 1.2.3 == 1.0-rc1 == 1.0-rc2 == 1.0.6 == 1.0.7 == 1.0.8 == 1.1-rc1 == 1.1-rc2 == 1.1-rc3 == 1.1-rc4 == 1.1.6 == 1.2.4 == 1.2.5 <= 1.2.6 == 1.2.3-rc1
CVE-2009-3701	Low	December 21, 2009 12/21/09	== 1.1 == 1.0 == 1.2.2 == 1.1.5 == 1.2.1 == 1.0.2 <= 1.2.4 == 1.0.1 == 1.0.5 == 1.1.1 == 1.0.3 == 1.1.3 == 1.0.4 == 1.2-rc1 == 1.2 == 1.1.4 == 1.1.2 == 1.2.3 == 1.0-rc1 == 1.0-rc2 == 1.0.6 == 1.0.7 == 1.0.8 == 1.1-rc1 == 1.1-rc2 == 1.1-rc3 == 1.1-rc4 == 1.1.6 == 1.2.3-rc1
CVE-2009-4363	Low	December 21, 2009 12/21/09	== 1.1 == 1.0 == 1.2.2 == 1.1.5 == 1.2.1 == 1.0.2 <= 1.2.4 == 1.0.1 == 1.0.5 == 1.1.1 == 1.0.3 == 1.1.3 == 1.0.4 == 1.2-rc1 == 1.2 == 1.1.4 == 1.1.2 == 1.2.3 == 1.0-rc1 == 1.0-rc2 == 1.0.6 == 1.0.7 == 1.0.8 == 1.1-rc1 == 1.1-rc2 == 1.1-rc3 == 1.1-rc4 == 1.1.6 == 1.2.3-rc1
CVE-2009-3236	Low	September 17, 2009 9/17/09	== 1.1 == 1.1-rc1 == 1.1-rc2 == 1.1-rc3 == 1.1-rc4 == 1.1.1 == 1.1.2 == 1.1.3 == 1.1.4 == 1.1.5 == 1.2 == 1.2-rc1 == 1.2.1 == 1.2.2 == 1.2.3 == 1.2.3-rc1
CVE-2009-3237	Low	September 17, 2009 9/17/09	== 1.1 == 1.1-rc1 == 1.1-rc2 == 1.1-rc3 == 1.1-rc4 == 1.1.1 == 1.1.2 == 1.1.3 == 1.1.4 == 1.1.6 == 1.2 == 1.2-rc1 == 1.2.1 == 1.2.2 == 1.2.3 == 1.2.3-rc1
CVE-2008-7218	High	September 13, 2009 9/13/09	== 1.1 == 1.0 == 1.0.2 == 1.0.1
CVE-2008-7219	High	September 13, 2009 9/13/09	== 1.1 == 1.0 == 1.0.2 == 1.0.1
CVE-2008-2783	Low	June 19, 2008 6/19/08	*
CVE-2008-1974	Low	April 27, 2008 4/27/08	== 1.0.5
CVE-2008-1284	Medium	March 11, 2008 3/11/08	<= 1.0.4
CVE-2008-0807	Low	February 19, 2008 2/19/08	== 1.0.3
CVE-2007-1679	Medium	March 26, 2007 3/26/07	== 1.0
CVE-2007-0579	Medium	January 30, 2007 1/30/07	== 1.0_rc3 == 1.0_rc2

nulllogic / groupware

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2009-2354	High		July 7, 2009 7/7/09	== 1.2.7

handysoft / groupware

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2021-26630	High		May 19, 2022 5/19/22	< 1.7.4.7 >= 2.0.0.0 < 2.0.3.7 >= 4.0.0.0 < 4.0.1.8
CVE-2020-7804	Medium		April 29, 2020 4/29/20	== 1.7.3.1

hanbiro / groupware

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2023-45800	High		December 13, 2023 12/13/23	>= 3.8.79 < 3.8.81.1

Showing vulnerabilities for 4 products matching "groupware". Each product has independent pagination.

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.