cve.bz

CVE-2026-65660 Microsoft SharePoint Code Injection Vulnerability

8.8 highKEVEPSS 9.9%Fix available

High (8.8) in Microsoft SharePoint. In CISA KEV since 2026-09-25. EPSS 9.9% estimated probability of exploitation activity in the next 30 days.

On this page
Improper control of generation of code ('code injection') in Microsoft Office SharePoint allows an authorized attacker to execute code over a network.

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
9.9% (unchanged from 9.9% a week ago; 2.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 96th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-09-25, due 2026-09-28
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2026-09-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-94 Improper Control of Generation of Code (Code Injection)
OWASP Top 10
A05:2025 Injection
Published
Modified
Assigned by
microsoft (CNA)
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-65660 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-65660?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-65660?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-65660 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-65660

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-65660](https://cve.bz/cve/badge/CVE-2026-65660.svg)](https://cve.bz/cve/CVE-2026-65660)

HTML:

<a href="https://cve.bz/cve/CVE-2026-65660"><img src="https://cve.bz/cve/badge/CVE-2026-65660.svg" alt="CVE-2026-65660"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft SharePoint Enterprise Server 2016from 16.0.0 before 16.0.5565.1001
Microsoft SharePoint Server 2019from 16.0.0 before 16.0.10417.20198
Microsoft SharePoint Server Subscription Editionfrom 16.0.0 before 16.0.19725.20522

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

Attack patterns (CAPEC)

  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High
  • CAPEC-77 Manipulating User-Controlled Variables Likelihood: High · Severity: Very High
  • CAPEC-242 Code Injection Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON