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.

328,409

Total vulnerabilities in the database

Vulnerabilities for products matching "evolution"

Found 7 matching products. Filters apply to all results.

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

ximian / evolution

8 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2005-0806	Medium	May 2, 2005 5/2/05	== 2.0.3
CVE-2003-0296	High	June 16, 2003 6/16/03	== 1.2.4
CVE-2003-0300	Medium	June 16, 2003 6/16/03	== 1.2.4
CVE-2002-1471	Medium	April 22, 2003 4/22/03	== 1.0.7 == 1.0.3 == 1.0.6 == 1.0.4 == 1.0.5 == 1.0.8
CVE-2003-0128	Medium	March 24, 2003 3/24/03	== 1.0.7 == 1.2.2 == 1.0.3 == 1.0.6 == 1.2 == 1.2.1 == 1.0.4 == 1.0.5 == 1.1.1 == 1.0.8
CVE-2003-0129	Medium	March 24, 2003 3/24/03	== 1.0.7 == 1.2.2 == 1.0.3 == 1.0.6 == 1.2 == 1.2.1 == 1.0.4 == 1.0.5 == 1.1.1 == 1.0.8
CVE-2003-0130	Medium	March 24, 2003 3/24/03	== 1.0.7 == 1.2.2 == 1.0.3 == 1.0.6 == 1.2 == 1.2.1 == 1.0.4 == 1.0.5 == 1.1.1 == 1.0.8
CVE-2002-1765	Medium	December 31, 2002 12/31/02	== 1.0.3 == 1.0.4

gnome / evolution

20 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2009-3721	High	May 26, 2021 5/26/21	*
CVE-2021-3349	Low	February 1, 2021 2/1/21	<= 3.38.3
CVE-2020-11879	Medium	April 17, 2020 4/17/20	< 3.35.91
CVE-2013-4166	High	February 6, 2020 2/6/20	<= 3.8.4
CVE-2018-15587	Low	February 11, 2019 2/11/19	<= 3.28.2
CVE-2016-10727	Medium	July 20, 2018 7/20/18	< 3.21.2
CVE-2018-12422	High	June 15, 2018 6/15/18	<= 3.29.2
CVE-2011-3201	Low	March 8, 2013 3/8/13	== 2.4 == 2.0.1 == 2.3.6 == 1.11 == 1.5 == 1.2.4 == 1.4.5 == 1.4.6 == 2.0.2 == 2.12.3 == 2.3.5 == 1.4.4 == 2.24.5 == 2.26.1 == 1.2.1 == 2.3.2 == 2.2 == 2.6 == 1.0.8 == 2.22.1 <= 3.0.3 == 2.32.3 == 2.26.3 == 2.8.1 == 2.12 == 2.1 == 1.4.3 == 2.3.6.1 == 1.2.2 == 2.10.3 == 2.28.3.1 == 2.22.3 == 2.3.1 == 2.4.2.1 == 2.24 == 1.4 == 2.30.3 == 2.0.0 == 2.3.7 == 2.3.3 == 1.2 == 2.3.4 == 2.0 == 1.2.3 == 2.2.1
CVE-2009-1631	Low	May 14, 2009 5/14/09	== 2.4 == 2.0.1 == 1.2.4 == 1.4.5 == 1.4.6 == 2.0.2 <= 2.26.1 == 1.4.4 == 1.2.1 == 2.6 == 1.0.8 == 2.12 == 1.4.3 == 1.2.2 == 2.24 == 1.4 == 2.0.0 == 1.2 == 1.2.3
CVE-2008-1108	High	June 4, 2008 6/4/08	== 2.2.1
CVE-2008-1109	High	June 4, 2008 6/4/08	== 2.22.1
CVE-2008-0072	Medium	March 6, 2008 3/6/08	<= 2.12.3
CVE-2007-3257	Medium	June 19, 2007 6/19/07	== 1.11
CVE-2007-1266	Medium	March 6, 2007 3/6/07	<= 2.8.1
CVE-2006-2789	Low	June 2, 2006 6/2/06	== 2.3.6 == 2.3.5 == 2.3.2 == 2.3.6.1 == 2.3.1 == 2.3.7 == 2.3.3 == 2.3.4
CVE-2006-0040	Medium	March 10, 2006 3/10/06	== 2.4.2.1
CVE-2006-0528	Medium	February 2, 2006 2/2/06	== 2.3.6 == 2.3.5 == 2.3.2 == 2.3.6.1 == 2.3.1 == 2.3.7 == 2.3.3 == 2.3.4
CVE-2005-2549	High	August 12, 2005 8/12/05	== 1.5 == 2.3.5 == 2.3.2 == 2.2 == 2.1 == 2.3.6.1 == 2.3.1 == 2.3.3 == 2.3.4 == 2.0
CVE-2005-2550	High	August 12, 2005 8/12/05	== 1.5 == 2.3.5 == 2.3.2 == 2.2 == 2.1 == 2.3.6.1 == 2.3.1 == 1.4 == 2.3.3 == 2.3.4 == 2.0
CVE-2005-0102	Critical	January 24, 2005 1/24/05	<= 2.0.2

evolution / evolution

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2009-0547	Medium		February 12, 2009 2/12/09	== 2.22.3.1

modxcms / evolution

4 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2011-0741	Low	February 2, 2011 2/2/11	== 0.9.6.1-p1 == 1.0.2 == 0.9.2.1 == 0.9.5 == 0.9.0 == 1.0.3 == 0.9.1 == 0.9.6.1 == 0.9.6 == 0.9.6.2 <= 1.0.4
CVE-2010-3929	High	February 2, 2011 2/2/11	== 0.9.6.1-p1 == 1.0.2 == 0.9.2.1 == 0.9.5 == 0.9.0 == 1.0.3 == 0.9.1 == 0.9.6.1 == 0.9.6 == 0.9.6.2 <= 1.0.4
CVE-2010-3930	Medium	February 2, 2011 2/2/11	== 0.9.6.1-p1 == 1.0.2 == 0.9.2.1 == 0.9.5 == 0.9.0 == 1.0.3 == 0.9.1 == 0.9.6.1 == 0.9.6 == 0.9.6.2 <= 1.0.4
CVE-2010-1427	Low	April 15, 2010 4/15/10	== 0.9.6.1-p1 == 0.9.2.1 <= 1.0.2 == 0.9.5 == 0.9.0 == 0.9.1 == 0.9.6.1 == 0.9.6 == 0.9.6.2

telligent / evolution

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2014-1223	Low		February 27, 2014 2/27/14	>= 6.1 < 6.1.19.36103 >= 7.1 < 7.1.12.36162 >= 7.5 <= 7.5.0.32466 >= 7.6 < 7.6.7.36651

evolutioncms / evolution

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2023-43340	Medium		October 19, 2023 10/19/23	<= 3.2.3
CVE-2023-43341	Medium		October 19, 2023 10/19/23	<= 3.2.3

cs-technologies / evolution

9 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2024-29842	High	April 15, 2024 4/15/24	<= 2.04.560
CVE-2024-29843	High	April 15, 2024 4/15/24	<= 2.04.560
CVE-2024-29844	Critical	April 15, 2024 4/15/24	<= 2.04.560
CVE-2024-29837	High	April 15, 2024 4/15/24	<= 2.04.560
CVE-2024-29838	High	April 15, 2024 4/15/24	<= 2.04.560
CVE-2024-29839	High	April 15, 2024 4/15/24	<= 2.04.560
CVE-2024-29840	High	April 15, 2024 4/15/24	<= 2.04.560
CVE-2024-29841	High	April 15, 2024 4/15/24	<= 2.04.560
CVE-2024-29836	Critical	April 15, 2024 4/15/24	<= 2.04.560

Showing vulnerabilities for 7 products matching "evolution". 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.