CVE-2023-33150

CRITICALNVD 9.69.6—

9.6

Microsoft Office Security Feature Bypass Vulnerability

CVSS v3: 9.6
EG Score: 9.6(medium)
EPSS: 43.8%
KEV: Not listed

Published

July 11, 2023

Last Modified

May 19, 2026

Advisory Details (1)

Auto-updated May 19, 2026

Patch available. Sources: microsoft.

microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-33150

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-693Protection Mechanism Failure

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Microsoft MSRCCVE-2023-331502023-07-11
Microsoft Office Security Feature Bypass Vulnerability

Data Freshness Timeline

(refreshed 14× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:12 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch

Frequently asked(5)

What is CVE-2023-33150?

CVE-2023-33150 is a critical vulnerability published on July 11, 2023. Microsoft Office Security Feature Bypass Vulnerability

When was CVE-2023-33150 disclosed?

CVE-2023-33150 was first published in the National Vulnerability Database on July 11, 2023, with the most recent update on May 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2023-33150 actively exploited?

CVE-2023-33150 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 43.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2023-33150?

CVE-2023-33150 has a CVSS v3 base score of 9.6 (NVD).

How do I remediate CVE-2023-33150?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-33150, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-33150

Explore →

Is Your Infrastructure Affected by CVE-2023-33150?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2023-33150

Published

Last Modified

Advisory Details (1)

Security Update Guide - Microsoft Security Response Center

Weakness Classification(1)

All Vendor Advisories

Data Freshness Timeline

Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2023-33150?

Same vendor

Same CWE

CVE-2023-33150

📅 Published

🔄 Last Modified

📋 Advisory Details (1)

Security Update Guide - Microsoft Security Response Center

Weakness Classification(1)

All Vendor Advisories

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2023-33150?

🔗 Related CVEs(same vendor + same CWE)

Same vendor

Same CWE

Published

Last Modified

Advisory Details (1)

Frequently asked(5)

Related CVEs(same vendor + same CWE)