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.

346,508

Total vulnerabilities in the database

Vulnerabilities for products matching "office"

Found 3 matching products. Filters apply to all results.

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

microsoft / office

2245 vulnerabilities found

Title	Severity	Date	Affected Version
CVE-2007-1747	High	May 8, 2007 5/8/07	== 2004 == xp-sp3 == 2003-sp2 == 2007 == 2000-sp3
CVE-2007-0035	High	May 8, 2007 5/8/07	== 2004 == xp-sp3 == 2003-sp2 == 2003 == 2000-sp3
CVE-2007-0215	High	May 8, 2007 5/8/07	== 2004 == xp-sp3 == 2003-sp2 == 2007 == 2000-sp3
CVE-2007-1238	Low	March 3, 2007 3/3/07	== 2003
CVE-2007-0208	High	February 13, 2007 2/13/07	== 2004 == xp-sp3 == 2003-sp2 == 2000-sp3
CVE-2007-0209	High	February 13, 2007 2/13/07	== 2004 == xp-sp3 == 2003-sp2 == 2000-sp3
CVE-2006-1311	High	February 13, 2007 2/13/07	== xp-sp3 == 2003-sp2 * == 2000-sp3
CVE-2007-0671	High	February 3, 2007 2/3/07	== 2004 == xp-sp3 == 2003-sp2 == 2000-sp3
CVE-2007-0515	High	January 26, 2007 1/26/07	== 2004 == xp-sp3 == 2003-sp2 == 2000-sp3
CVE-2007-0028	High	January 9, 2007 1/9/07	== 2000-sp3 == xp-sp3 == 2003-sp2 == 2004 *
CVE-2007-0029	High	January 9, 2007 1/9/07	== 2000-sp3 == xp-sp3 == 2003-sp2 == 2004 *
CVE-2007-0030	High	January 9, 2007 1/9/07	== 2000-sp3 == xp-sp3 == 2003-sp2 == 2004 *
CVE-2007-0031	High	January 9, 2007 1/9/07	== 2000-sp3 == xp-sp3 == 2003-sp2 == 2004 *
CVE-2007-0033	High	January 9, 2007 1/9/07	== 2000-sp3 == xp-sp3 == 2003-sp2
CVE-2007-0034	High	January 9, 2007 1/9/07	== 2000-sp3 == xp-sp3 == 2003-sp2
CVE-2007-0027	High	January 9, 2007 1/9/07	== 2000-sp3 == xp-sp3 == 2003-sp2 == 2004 *
CVE-2006-1305	Low	December 31, 2006 12/31/06	== 2000-sp3 == xp-sp3 == 2003-sp2
CVE-2006-5574	High	December 31, 2006 12/31/06	== 2003-sp2
CVE-2006-6561	High	December 14, 2006 12/14/06	== 2004 == xp-sp3 == 2003-sp2 == 2000-sp3
CVE-2006-6456	High	December 11, 2006 12/11/06	== 2004 == xp-sp3 == 2003-sp2 == 2000-sp3
CVE-2006-5994	High	December 6, 2006 12/6/06	== 2004 == xp-sp3 == 2003-sp2 == 2000-sp3
CVE-2006-2387	Medium	October 10, 2006 10/10/06	== 2003-sp1 == 2001-sr1 == 2004 == 2000 == 2003-sp2 == 2001 * == 2000-sp1 == 2000-sp2 == 2003 == 2003-sp3 == 2000-sp3
CVE-2006-3434	High	October 10, 2006 10/10/06	== 2003-sp1 == 2000 == 2003-sp2 * == 2000-sp1 == 2000-sp2 == 2003-sp3 == 2000-sp3 == 2003 == 2004
CVE-2006-3647	High	October 10, 2006 10/10/06	== 2003-sp1 == 2000 == 2003-sp2 == 2001 * == 2000-sp1 == 2000-sp2 == 2003-sp3 == 2000-sp3 == 2003 == 2004 == 2001-sr1
CVE-2006-3650	High	October 10, 2006 10/10/06	== 2003-sp1 == 2000 == 2003-sp2 == 2001 * == 2000-sp1 == 2000-sp2 == 2003 == 2003-sp3 == 2000-sp3 == 2001-sr1 == 2004
CVE-2006-3651	High	October 10, 2006 10/10/06	== 2003
CVE-2006-3864	High	October 10, 2006 10/10/06	== 2003-sp1 == 2004 == xp-sp3 == 2003-sp2 * == 2000-sp3
CVE-2006-3868	Medium	October 10, 2006 10/10/06	== 2003 == xp
CVE-2006-3877	High	October 10, 2006 10/10/06	== 2004 == xp-sp3 == 2003-sp2 == 2000-sp3
CVE-2006-4693	High	October 10, 2006 10/10/06	*
CVE-2006-3435	High	October 10, 2006 10/10/06	== 2003-sp1 == 2004 == xp-sp3 == 2000 == 2003-sp2 == xp-sp2 * == 2000-sp1 == 2000-sp2 == 2003 == 2003-sp3 == xp == xp-sp1 == 2000-sp3
CVE-2006-3876	High	October 10, 2006 10/10/06	== 2003-sp1 == 2000 == 2003-sp2 == 2001 == 2000-sp1 == 2000-sp2 == 2003 == 2003-sp3 == 2000-sp3 == 2001-sr1 == 2004
CVE-2006-4694	High	September 27, 2006 9/27/06	== 2000 * == xp-sp2 == 2000-sp1 == 2000-sp2 == 2003 == xp-sp1 == 2000-sp3
CVE-2006-0001	High	September 12, 2006 9/12/06	== 2003-sp1 == xp-sp3 == 2003-sp2 == 2000-sp3
CVE-2006-4534	High	September 5, 2006 9/5/06	== 2003-sp1 == 2000 == 2003-sp2 == 2001 == 2000-sp1 == 2000-sp2 == 2003 == 2003-sp3 == 2000-sp3 == 2001-sr1
CVE-2006-0007	High	July 11, 2006 7/11/06	== 2003-sp1 == xp-sp3 == 2003-sp2 == 2000-sp3
CVE-2006-0033	High	July 11, 2006 7/11/06	== 2003-sp1 == xp-sp3 == 2003-sp2 == 2000-sp3
CVE-2006-1316	High	July 11, 2006 7/11/06	== 2003-sp1 == xp-sp3 == 2003-sp2 == 2000-sp3
CVE-2006-2389	High	July 11, 2006 7/11/06	== 2003-sp1 == xp-sp3 == 2003-sp2 == 2000-sp3
CVE-2006-3493	Medium	July 10, 2006 7/10/06	== 2003-sp1 == xp-sp3 == 2000 == 2003-sp2 == xp-sp2 == 2000-sp1 == 2000-sp2 == 2003 == 2003-sp3 == xp == xp-sp1 == 2000-sp3
CVE-2006-2492	High	May 20, 2006 5/20/06	== 2003-sp1 == xp-sp3 == 2003-sp2 == 2000-sp3
CVE-2006-1540	High	March 30, 2006 3/30/06	== 2003-sp1 == xp-sp3 == 2000 == 2003-sp2 * == xp-sp2 == 2000-sp1 == xp-sp1 == 2000-sp3 == 2003 == 2004
CVE-2006-0009	Medium	March 14, 2006 3/14/06	== 2003-sp1 == 2004 == xp-sp3 == 2003-sp2 * == 2000-sp3
CVE-2006-0028	Medium	March 14, 2006 3/14/06	== 2003-sp1 == 2004 == xp-sp3 == 2003-sp2 * == 2000-sp3
CVE-2006-0029	Medium	March 14, 2006 3/14/06	== 2003-sp1 == 2004 == xp-sp3 == 2003-sp2 * == 2000-sp3
CVE-2006-0030	Medium	March 14, 2006 3/14/06	== 2003-sp1 == 2004 == xp-sp3 == 2003-sp2 * == 2000-sp3
CVE-2006-0031	Medium	March 14, 2006 3/14/06	== 2003-sp1 == 2004 == xp-sp3 == 2003-sp2 * == 2000-sp3
CVE-2006-0004	Medium	February 14, 2006 2/14/06	== 2000-sp3
CVE-2006-0008	High	February 14, 2006 2/14/06	== 2003-sp1 == 2003-sp2 == 2003
CVE-2006-0002	High	January 10, 2006 1/10/06	== 2003-sp1 == xp-sp3 == 2003-sp2 == 2000-sp3

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