LiveActive security incident?Get immediate response
CVE Record

CVE-2021-1711: Microsoft Office Remote Code Execution Vulnerability

Microsoft Office Remote Code Execution Vulnerability

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-1711 is a Microsoft Office remote code execution vulnerability affecting several Office versions. Successful exploitation could let an attacker run code with the user’s permissions, but the CVSS data indicates user interaction is required. Treat this as important endpoint patching work, especially where Office is widely deployed.

Executive priority

Prioritize remediation as a high-severity endpoint risk. The business concern is user-driven code execution through Office on unpatched machines, not confirmed active exploitation. Patch through normal emergency or accelerated desktop update processes based on asset exposure and Office prevalence.

Technical view

The source bundle identifies affected Microsoft Office 2010 SP2, 2013 SP1, 2016, 2019, and Microsoft 365 Apps for Enterprise versions. CVSS 3.1 score is 7.8: local attack vector, low complexity, no privileges required, user interaction required, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is primarily on endpoints running the listed Microsoft Office products without the relevant Microsoft security update. Internet-facing servers are not indicated by the provided CVSS vector. Risk is broader in environments where users frequently receive or open Office content from external or untrusted sources.

Exploitation context

The bundle does not show CISA KEV listing or cited evidence of active exploitation. CVSS exploit maturity is listed as unproven. Based on the vector, exploitation requires user interaction on an affected Office installation, but the provided sources do not describe a specific trigger or exploitation method.

Researcher notes

The public bundle is sparse: no CWE, exploit narrative, affected build ranges, or KB identifiers are included here. The strongest grounded details are Microsoft’s affected product list, CVSS vector, official remediation level, and absence of KEV evidence. Avoid asserting exploit mechanics beyond required user interaction.

Mitigation direction

  • Apply Microsoft’s official security update guidance for CVE-2021-1711.
  • Prioritize endpoints running affected Office versions listed in the advisory.
  • Confirm Microsoft 365 Apps update channels are receiving security updates.
  • Reduce user exposure to untrusted Office content until patching is complete.
  • Check vendor guidance for any product-specific servicing details.

Validation and detection

  • Inventory Office 2010 SP2, 2013 SP1, 2016, 2019, and Microsoft 365 Apps installations.
  • Verify installed Office builds against Microsoft’s CVE-2021-1711 update guidance.
  • Confirm endpoint vulnerability scanners no longer report CVE-2021-1711.
  • Review patch management records for January 2021 Office security updates.
  • Spot-check high-risk user systems where Office documents are frequently handled.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-1711 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2021-1711Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftMicrosoft Office 201919.0.0Listed
MicrosoftMicrosoft 365 Apps for Enterprise16.0.1Listed
MicrosoftMicrosoft Office 201616.0.0Listed
MicrosoftMicrosoft Office 2010 Service Pack 213.0.0.0Listed
MicrosoftMicrosoft Office 2013 Service Pack 115.0.0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.