dbcve.org
365 AppsApplication · Microsoft

CVE-2022-47213

HIGH · 7.8 CVSS v3.1 Published 2022-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Microsoft Office Graphics Remote Code Execution Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a remote code execution vulnerability in the Microsoft Office graphics component. The vulnerability allows an attacker to execute arbitrary code by convincing a user to open a specially crafted Office document that triggers a flaw in graphics rendering.

MitigationApply Microsoft security updates for Microsoft Office to patch the vulnerability. Users should avoid opening untrusted Office documents and enable Protected View for documents from unknown sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
365 AppsApplication
Affected:all versions

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Microsoft Office installation
    Open Word or Excel, go to File > Account > About [App] to see the version number, or run 'winword /?' from Command Prompt
    Affected if Microsoft 365 Apps or any Office application is installed and version cannot be verified as patched via Windows Update
  2. Check Windows Update status for Office
    Open Settings > Update & Security > Windows Update > View update history, or check Office's File > Account > Update Options > Update Now
    Affected if Recent Office security updates are not installed or update status shows 'Update Available' pending installation
  3. Verify Protected View settings
    Go to File > Options > Trust Center > Trust Center Settings > Protected View, check if all three options (Internet, Intranet, Unsanctioned) are enabled
    Affected if Protected View is disabled for any of the three source locations, or Trust Center settings are inaccessible indicating potential policy override
  4. Check macro execution settings for Office files
    Go to File > Options > Trust Center > Trust Center Settings > Macro Settings, verify setting is not 'Enable all macros' or check via group policy at Computer Configuration > Administrative Templates > Microsoft Office [version] > Security Settings
    Affected if Macros are set to enable automatically without notification or trusted location restrictions are not configured

Your environment is affected if Microsoft 365 Apps or Office is installed without the CVE-2022-47213 security patch applied AND Protected View is disabled, allowing untrusted documents to render graphics without sandbox protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates for Microsoft Office to patch the vulnerability. Users should avoid opening untrusted Office documents and enable Protected View for documents from unknown sources.

Recommended fix Moderate confidence

Microsoft 365 Apps Current Channel (monthly updates) - apply the December 2022 security updates

  1. Check Microsoft 365 Apps update channel status by going to File > Account in any Office application
  2. Ensure automatic updates are enabled for Microsoft 365 Apps
  3. Run Office Update: Go to File > Account > Update Options > Update Now
  4. Alternatively, use the Microsoft Update service at https://portal.office.com/portal/adminportal
  5. Verify the patch was applied by checking the Office version after updating
  6. For enterprise deployments, verify through your admin center that the latest security updates for Microsoft 365 Apps are installed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in 365 Apps Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-47213 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-47213 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data