CVE-2025-59252VulnerabilityPublished 9 Oct 2025Updated 26 Feb 2026

CVE-2025-59252: Microsoft 365 Word Copilot · Command Injection

Affects Microsoft 365 Word CopilotSource CVE Database V5

Not known to be exploited · CVSS 9.3 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score

9.3Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 46% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: High
Integrity: Low
Availability: None

Temporal metrics

Exploit Code Maturity: Unproven
Remediation Level: Official Fix
Report Confidence: Confirmed

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact on the impacted component.
Availability: None: There is no impact to availability within the impacted component.
Exploit Code Maturity: Unproven: No exploit code is available, or an exploit is theoretical.
Remediation Level: Official Fix: A complete vendor solution is available. Either the vendor has issued an official patch, or an upgrade is available.
Report Confidence: Confirmed: Detailed reports exist, or functional reproduction is possible (functional exploits may provide this). Source code is available to independently verify the assertions of the research, or the author or vendor of the affected code has confirmed the presence of the vulnerability.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Organizations should monitor Microsoft security advisories closely and apply patches or updates for Microsoft 365 Word Copilot as soon as they become available. In the interim, network-level defenses such as intrusion detection and prevention systems (IDS/IPS) should be configured to detect and block anomalous command injection patterns targeting Word Copilot. Restricting network access to Microsoft 365 services to trusted IP ranges and enforcing strict egress filtering can reduce exposure. Employing application-layer firewalls and enabling advanced threat protection features within Microsoft 365 can help identify suspicious activities. Administrators should audit and limit permissions related to document automation and AI features to minimize potential exploitation scope. User education on recognizing unusual document behavior and reporting anomalies can aid early detection. Finally, organizations should implement robust logging and monitoring of Microsoft 365 activities to facilitate rapid incident response if exploitation attempts occur.

Description

Improper neutralization of special elements used in a command ('command injection') in Copilot allows an unauthorized attacker to disclose information over a network.

Impact

The primary impact of CVE-2025-59252 is the unauthorized disclosure of sensitive information, which can lead to data breaches, loss of intellectual property, and exposure of confidential communications. Since the vulnerability can be exploited remotely without authentication or user interaction, it significantly increases the risk of widespread exploitation. Organizations using Microsoft 365 Word Copilot, especially those handling sensitive or regulated data, face heightened risks of confidentiality compromise. The integrity of documents is minimally affected, and availability remains intact, but the breach of confidentiality alone can have severe legal, financial, and reputational consequences. The vulnerability could also be leveraged as a foothold for further attacks within a network if combined with other vulnerabilities or misconfigurations. Given Microsoft 365's global adoption, the threat has a broad potential impact, particularly in sectors such as government, finance, healthcare, and critical infrastructure where document confidentiality is paramount.

CWE-77Improper Neutralization of Special Elements used in a Command ('Command Injection') (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #23OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
Architecture and Design
If at all possible, use library calls rather than external processes to recreate the desired functionality.
Implementation
If possible, ensure that all external commands called from the program are statically created.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
LDAP Injection (opens in a new tab)
Command Delimiters (opens in a new tab)
IMAP/SMTP Command Injection (opens in a new tab)
Manipulating Writeable Terminal Devices (opens in a new tab)
Exploiting Multiple Input Interpretation Layers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

msrc.microsoft.com/update-guide/vulnerability/CVE-2025-59252 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 27 Feb 2026, 03:57 UTC

WeaknessesCWE-77

Technical details

References

Community reviews

Related threats