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

Found 1 matching product.

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

foxitsoftware / foxit_reader

372 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2016-4064	Medium	April 22, 2016 4/22/16	<= 7.3.0.118
CVE-2016-4063	Medium	April 22, 2016 4/22/16	<= 7.3.0.118
CVE-2016-4062	Low	April 22, 2016 4/22/16	<= 7.3.0.118
CVE-2016-4061	Medium	April 22, 2016 4/22/16	<= 7.3.0.118
CVE-2016-4060	Medium	April 22, 2016 4/22/16	<= 7.3.0.118
CVE-2016-4059	Medium	April 22, 2016 4/22/16	<= 7.3.0.118
CVE-2015-8843	Medium	April 13, 2016 4/13/16	== 7.0 == 7.0.6 == 7.2 == 6.2 == 6.1.2 == 6.1.4 == 7.0.1 == 6.2.1 == 7.1.5 == 6.1
CVE-2015-8580	Medium	December 16, 2015 12/16/15	<= 7.2.0.722
CVE-2015-3633	Medium	May 1, 2015 5/1/15	== 7.1.0.306 <= 7.1.3.320
CVE-2015-3632	Low	May 1, 2015 5/1/15	<= 7.1.3.320
CVE-2015-2790	Low	March 30, 2015 3/30/15	<= 7.0.6.1126
CVE-2015-2789	Low	March 30, 2015 3/30/15	== 7.0 == 7.0.6 == 6.2 == 6.1.2 == 6.1.4 == 6.2.1 == 6.1
CVE-2012-4759	Medium	September 6, 2012 9/6/12	== 5.3.1.0606
CVE-2012-4337	High	August 23, 2012 8/23/12	<= 5.1.4.0104 == 2.0 == 2.3 == 3.0 == 3.1.2.1013 == 3.1.2.1030 == 3.2.0.0303 == 3.2.1.0401 == 4.0 == 4.0.0.0619 == 4.1 == 4.1.1.0805 == 4.2 == 4.3 == 4.3.1.0218 == 5.0 == 5.0.2 == 5.1.0.1021 == 5.1.3
CVE-2011-3691	High	September 27, 2011 9/27/11	== 4.1.1 == 4.2 == 3.1 == 2.2 == 4.3 == 2.0 <= 5.0 == 3.3.1 == 3.1.4 == 3.1.1 == 2.3 == 3.1.3 == 3.2 == 3.0 == 3.2.1 == 4.0
CVE-2011-1908	High	June 24, 2011 6/24/11	== 3.1 == 2.2 == 2.0 == 3.3.1 == 3.1.4 == 3.1.1 <= 4.0 == 2.3 == 3.1.3 == 3.2 == 3.0 == 3.2.1
CVE-2011-0332	High	February 25, 2011 2/25/11	<= 4.3 == 2.0 == 2.2 == 2.3 == 3.0 == 3.1 == 3.1.1 == 3.1.3 == 3.1.4 == 3.2 == 3.2.1 == 3.3.1 == 4.0 == 4.1.1
CVE-2010-1239	High	April 5, 2010 4/5/10	== 3.1.1.0928 == 3.1.1.0901 == 2.3 == 3.1.3.1030 == 3.1.0.0824 <= 3.2.0.0303 == 3.0
CVE-2009-0690	High	June 23, 2009 6/23/09	== 3.0 == 3.0.2009.1301
CVE-2009-0691	High	June 23, 2009 6/23/09	== 3.0
CVE-2009-0191	High	March 10, 2009 3/10/09	== 3.0.2009.1301 == 2.3 == 3.0
CVE-2008-1104	High	May 21, 2008 5/21/08	<= 2.3 == 2.2 == 2.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.