Vulnerability Database

422,960

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

1073 vulnerabilities found
Title Severity Exploit Date Affected versions
High August 15, 2015 8/15/15
= 2007-sp3
= 2010-sp2
High August 15, 2015 8/15/15
= 2007-sp3
= 2010-sp2
High August 15, 2015 8/15/15
= 2007-sp3
= 2010-sp2
High August 15, 2015 8/15/15
= 2010-sp2
Medium August 15, 2015 8/15/15
= 2010-sp2
High August 15, 2015 8/15/15
= 2007-sp3
= 2010-sp2
= 2013-sp1
High July 14, 2015 7/14/15
= 2007-sp3
= 2010-sp2
= 2011
= 2013-sp1
High July 14, 2015 7/14/15
= 2010-sp2
High July 14, 2015 7/14/15
= 2010-sp2
= 2011
High July 14, 2015 7/14/15
= 2011
High June 10, 2015 6/10/15
= 2013-sp1
High June 10, 2015 6/10/15
= 2010-sp2
= 2013-sp1
High May 13, 2015 5/13/15
= 2007-sp3
High May 13, 2015 5/13/15
= 2010-sp2
= 2011
= 2013-sp1
High April 14, 2015 4/14/15
= 2010-sp2
High April 14, 2015 4/14/15
= 2010-sp2
High April 14, 2015 4/14/15
= 2010-sp2
Medium April 14, 2015 4/14/15
= 2011
High March 11, 2015 3/11/15
= 2010-sp2
High March 11, 2015 3/11/15
= 2010-sp2
= 2013
= 2013-sp1
High February 11, 2015 2/11/15
= 2010-sp2
High February 11, 2015 2/11/15
= 2010-sp2
Medium February 11, 2015 2/11/15
= 2007-sp3
= 2010-sp2
= 2013
= 2013-sp1
High December 11, 2014 12/11/14
= 2007-sp3
= 2010-sp2
= 2013
= 2013-sp1
= 2013-sp2
High December 11, 2014 12/11/14
= 2010-sp2
= 2011
= 2013
= 2013-sp1
High October 15, 2014 10/15/14
= 2007-sp3
= 2010-sp1
= 2010-sp2
= 2011
High September 19, 2014 9/19/14
= 2000-sp1
= 2000-sp2
= 2004
= x
= xp-sp3
High May 14, 2014 5/14/14
= 2007-sp3
= 2010-sp1
= 2010-sp2
= 2013
= 2013-sp1
Medium May 14, 2014 5/14/14
= 2013
= 2013-sp1
Medium May 14, 2014 5/14/14
= 2007-sp3
= 2010-sp1
= 2010-sp2
= 2013
= 2013-sp1
Medium April 5, 2014 4/5/14
= 2007-sp3
= 2010-sp1
= 2010-sp2
= 2011
= 2013
High March 25, 2014 3/25/14
= 2011
Medium December 11, 2013 12/11/13
= 2013
Medium December 11, 2013 12/11/13
= 2007-sp3
= 2010-sp1
= 2010-sp2
High November 13, 2013 11/13/13
= 2003-sp3
= 2007-sp3
High November 13, 2013 11/13/13
= 2003-sp3
= 2007-sp3
= 2010-sp1
= 2013
High November 13, 2013 11/13/13
= 2003-sp3
= 2007-sp3
High November 6, 2013 11/6/13
= 2003-sp3
= 2007-sp3
= 2010-sp1
= 2010-sp2
High October 9, 2013 10/9/13
= 2007-sp3
= 2010-sp1
= 2011
= 2013
High September 11, 2013 9/11/13
= 2011
Medium September 11, 2013 9/11/13
= 2003-sp3
= 2007-sp3
High September 11, 2013 9/11/13
= 2007-sp3
High September 11, 2013 9/11/13
= 2007-sp3
Medium September 11, 2013 9/11/13
= 2010-sp1
High July 10, 2013 7/10/13
= 2003-sp3
= 2007-sp3
= 2010-sp1
High June 12, 2013 6/12/13
= 2003-sp3
= 2011
Medium March 13, 2013 3/13/13
= 2008
= 2011
High January 9, 2013 1/9/13
= 2003-sp3
= 2007-sp2
= 2007-sp3
High January 9, 2013 1/9/13
= 2003-sp3
= 2007-sp2
= 2007-sp3
High November 14, 2012 11/14/12
= 2008
= 2011

Showing vulnerabilities for 3 products matching "office". Each product has independent pagination.

Running office on internet-facing hosts?

Knowing a product's CVEs is half the job; the other half is knowing every place it is exposed. Attack surface management continuously maps your external assets and the software they run.

What is attack surface management? →

Frequently Asked Questions

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.