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 June 17, 2023 6/17/23
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
High June 17, 2023 6/17/23
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
High June 14, 2023 6/14/23
= 2019
>= 16.0.0, < 16.74.23061100
High June 14, 2023 6/14/23
= 2013-sp1
= 2016
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
High June 14, 2023 6/14/23
>= 19.0.0, < https://aka.ms/officesecurityreleases
>= 16.0.0, < 16.74.23061100
High June 14, 2023 6/14/23
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
High June 14, 2023 6/14/23
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
>= 16.0.0, < 16.74.23061100
High June 5, 2023 6/5/23
= 2019
>= 16.0.0, < 16.73.23051401
High June 1, 2023 6/1/23
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
High May 9, 2023 5/9/23
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
Low May 9, 2023 5/9/23
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
High May 9, 2023 5/9/23
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
>= 16.0.0, < 16.73.23051401
High April 11, 2023 4/11/23
= 2019
>= 16.0.0, < 16.72.23040900
High April 11, 2023 4/11/23
= 2019
>= 16.0.0, < 16.72.23040900
High March 14, 2023 3/14/23
= 2019
>= 16.0.0, < 16.71.23031200
>= 16.0.1, < 16.0.16026.20172
>= 16.0.1, < 16.0.14606.20000
High March 14, 2023 3/14/23
= 2013-sp1
= 2016
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
>= 16.0.0, < 16.71.23031200
>= 16.0.0, < 16.0.5387.1000
>= 15.0.0, < 15.0.5537.1000
High March 14, 2023 3/14/23
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
Critical March 14, 2023 3/14/23
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
Medium March 14, 2023 3/14/23
>= 16.0.1, < 16.0.16026.20172
High February 14, 2023 2/14/23
>= 16.0.1, < 16.0.16130.20156
>= 16.0.1, < 16.0.14326.21330
>= 2.0.0, < 2.70.23021003
Critical February 14, 2023 2/14/23
= 2019
>= 16.0.0, < 16.70.23021201
>= 19.0.0, < https://aka.ms/officesecurityreleases
High January 10, 2023 1/10/23
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
High January 10, 2023 1/10/23
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
High January 10, 2023 1/10/23
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
High January 10, 2023 1/10/23
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
High January 10, 2023 1/10/23
= 2019
>= 16.0.0, < 16.69.23010700
High January 10, 2023 1/10/23
= 2019
>= 16.0.0, < 16.69.23010700
High December 13, 2022 12/13/22
= 2019
High December 13, 2022 12/13/22
= 2019
High December 13, 2022 12/13/22
= 2019
High December 13, 2022 12/13/22
= 2019
High December 13, 2022 12/13/22
= 2019
High December 13, 2022 12/13/22
= 2019
High November 9, 2022 11/9/22
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
>= 16.0.0, < 16.67.22111300
High November 9, 2022 11/9/22
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
Medium November 9, 2022 11/9/22
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
Medium November 9, 2022 11/9/22
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
Medium November 9, 2022 11/9/22
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
High November 9, 2022 11/9/22
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
High November 9, 2022 11/9/22
= 2019
>= 16.0.0, < 16.67.22111300
Medium November 9, 2022 11/9/22
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
Low October 11, 2022 10/11/22
= 2019
>= 16.0.0, < 16.66.22100900
High October 11, 2022 10/11/22
= 2019
>= 16.0.0, < 16.66.22100900
High October 11, 2022 10/11/22
= 2013-sp1
= 2016
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
>= 16.0.0, < 16.66.22100900
>= 16.0.0, < 16.0.5365.1000
>= 15.0.0, < 15.0.5493.1000
High October 11, 2022 10/11/22
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
Medium October 11, 2022 10/11/22
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
High September 13, 2022 9/13/22
= 2013-sp1
= 2016
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
>= 16.0.0, < 16.65.22091101
>= 16.0.0, < 16.0.5361.1000
>= 15.0.0, < 15.0.5485.1000
High September 13, 2022 9/13/22
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
High September 13, 2022 9/13/22
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
High August 9, 2022 8/9/22
= 2013-sp1
= 2016
= 2019
>= 19.0.0, < https://aka.ms/officesecurityreleases
>= 16.0.0, < 16.0.14931.20612
>= 15.0.0, < 15.0.5475.1001

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.