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

Found 12 matching products. Filters apply to all results.

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

apple / mail

4 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2010-3887	Low	October 8, 2010 10/8/10	*
CVE-2008-4491	Medium	October 8, 2008 10/8/08	== 3.5
CVE-2008-0039	Medium	February 12, 2008 2/12/08	*
CVE-2005-2512	Low	August 19, 2005 8/19/05	*

chilkat_software / mail

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2008-4584	Medium		October 15, 2008 10/15/08	== 7.8

pear / mail

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2009-4111	Medium		November 29, 2009 11/29/09	== 1.1.14 == 1.2.0b2

mikel_lindsaar / mail

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2011-0739	Medium		February 2, 2011 2/2/11	== 1.4.3 == 1.2.8 == 2.2.5.1 == 2.2.4 == 2.2.5 == 1.3.1 == 1.5.1 == 2.1.5.2 == 2.1.1 == 1.2.5 == 1.2.7 == 1.5.0 == 1.3.5 == 1.2.9 == 2.1.3 == 2.2.10 == 1.3.4 == 1.1.0 == 2.2.6 == 1.4.0 == 2.2.0 == 1.5.3 == 1.6.0 == 2.0.3 == 2.1.0 == 1.3.3 == 1.4.2 == 1.5.2 == 1.0.0 == 1.5.4 == 1.3.0 == 1.4.1 == 2.2.13 == 2.2.9 == 1.2.1 == 2.2.11 == 2.2.3 <= 2.2.14 == 2.2.9.1 == 2.1.5.3 == 2.2.2 == 2.0.5 == 2.1.2 == 1.3.2 == 2.2.1 == 2.1.5 == 2.2.7 == 2.2.12 == 2.2.6.1 == 2.2.5.2 == 2.1.5.1 == 1.2.6

htc / mail

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2013-10001	Low		May 17, 2022 5/17/22	== 5.2.2222282614.528614.528614 == 5.5.550363

mail_project / mail

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2015-9097	Low		June 12, 2017 6/12/17	<= 2.5.4

basercms / mail

2 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2016-4877	Medium		May 12, 2017 5/12/17	== 3.0.10
CVE-2016-4879	High		May 12, 2017 5/12/17	<= 3.0.10

zetacomponents / mail

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2017-15806	Medium		November 15, 2017 11/15/17	< 1.8.2

claws-mail / mail

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2019-10735	Low		April 7, 2019 4/7/19	== 3.14.1

egain / mail

1 vulnerabilities found

Title	Severity	Exploit	Date	Affected Version
CVE-2019-17123	High		December 13, 2019 12/13/19	== 11

nextcloud / mail

15 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2025-66514	Low	December 5, 2025 12/5/25	< 5.5.3
CVE-2024-52508	High	November 15, 2024 11/15/24	>= 1.9.0 < 1.14.6 >= 1.15.0 < 1.15.4 >= 2.1.0 < 2.2.11 >= 3.1.0 < 3.6.3 >= 3.7.0 < 3.7.7
CVE-2024-52509	Low	November 15, 2024 11/15/24	>= 2.2.0 < 2.2.10 >= 3.6.0 < 3.6.2 >= 3.7.0 < 3.7.2
CVE-2023-48307	Low	November 21, 2023 11/21/23	>= 3.0.0 < 3.3.0 >= 1.13.0 < 2.2.8
CVE-2023-45660	Low	October 16, 2023 10/16/23	>= 3.0.0 < 3.3.0 >= 2.2.0 < 2.2.8
CVE-2023-33184	Low	May 27, 2023 5/27/23	>= 2.2.0 < 2.2.5 >= 2.3.0 < 3.0.2 >= 1.13.0 < 1.15.3
CVE-2023-25160	Low	February 13, 2023 2/13/23	< 1.11.8 >= 1.12.0 < 1.12.9 >= 1.13.0 < 1.14.5 >= 2.0.0 < 2.2.1
CVE-2023-23943	Medium	February 6, 2023 2/6/23	>= 2.2.0 < 2.2.2 < 1.15.0
CVE-2023-23944	Low	February 6, 2023 2/6/23	< 2.2.2
CVE-2022-31119	Low	August 4, 2022 8/4/22	< 1.12.1
CVE-2022-31132	High	August 4, 2022 8/4/22	>= 1.13.0 < 1.13.6 < 1.12.8
CVE-2021-39220	Low	October 25, 2021 10/25/21	< 1.10.4
CVE-2021-32707	Low	July 12, 2021 7/12/21	< 1.9.6
CVE-2021-32652	High	June 1, 2021 6/1/21	>= 1.5.5 < 1.8.2 < 1.4.3
CVE-2020-8156	High	May 12, 2020 5/12/20	< 1.1.4

mail

4 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2015-9097	Low	June 12, 2017 6/12/17	< 2.5.5
CVE-2012-2139	Medium	July 18, 2012 7/18/12	< 2.4.4
CVE-2012-2140	High	July 18, 2012 7/18/12	< 2.4.3
CVE-2011-0739	Medium	February 2, 2011 2/2/11	< 2.2.15

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