Skip to main content
CVE-2023-36762VulnerabilityPublished Updated

CVE-2023-36762: Microsoft SharePoint Enterprise Server 2016 · Improper Input Validation

Affects Microsoft SharePoint Enterprise Server 2016Source CVE Database V5

0

Not known to be exploited · CVSS 7.3 High.

Data as of 26 Oct 2026, 07:57 UTC

CVSS 3.1 base score
7.3High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 57% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:L/E:U/RL:O/RC:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Sep 2023

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Microsoft Microsoft SharePoint Enterprise Server 2016Affected
  • =16.0.0
Fixed in–

AI-suggested

1. Monitor Microsoft security advisories closely and apply official patches or updates for SharePoint Enterprise Server 2016 as soon as they become available. 2. Until patches are released, restrict the ability to upload or preview Microsoft Word documents in SharePoint libraries, especially from untrusted or external sources. 3. Implement strict input validation and scanning of uploaded documents using advanced anti-malware and sandboxing solutions to detect malicious content. 4. Enforce the principle of least privilege on SharePoint service accounts to limit potential damage from code execution. 5. Educate users about the risks of opening suspicious or unexpected Word documents, emphasizing the need for caution even within internal networks. 6. Employ network segmentation and access controls to limit local network access to SharePoint servers, reducing the likelihood of exploitation. 7. Enable detailed logging and monitoring on SharePoint servers to detect anomalous activities indicative of exploitation attempts. 8. Consider disabling or limiting the use of legacy or unnecessary SharePoint features that process Word documents if feasible. 9. Conduct regular security assessments and penetration testing focused on SharePoint environments to identify and remediate weaknesses proactively.

Description

Microsoft Word Remote Code Execution Vulnerability

References

Community reviews

Loading reviews…