cve.bz

CVE-2016-0025 microsoft: Improper Input Validation

7.3 highEPSS 17%

High (7.3) in microsoft. EPSS 17% estimated probability of exploitation activity in the next 30 days.

On this page
Microsoft Word 2007 SP3, Office 2010 SP2, Word 2010 SP2, Word 2013 SP1, Word 2013 RT SP1, Office 2016, Word 2016, Word for Mac 2011, Word 2016 for Mac, Office Compatibility Pack SP3, Word Automation Services on SharePoint Server 2010 SP2, Word Automation Services on SharePoint Server 2013 SP1, Office Web Apps 2010 SP2, Office Web Apps Server 2013 SP1, and Office Online Server allow remote attackers to execute arbitrary code via a crafted Office document, aka "Microsoft Office Memory Corruption Vulnerability."

Severity

CVSS 3.0

7.3 high
CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
EPSS
17% (unchanged from 17% a week ago; 17% 30 days ago) estimated probability of exploitation activity in the next 30 days; 97th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-15. 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-20 Improper Input Validation
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2016-0025 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2016-0025?via=ask-ai-copy and https://cve.bz/cve/CVE-2016-0025?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-2016-0025 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-2016-0025

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-2016-0025](https://cve.bz/cve/badge/CVE-2016-0025.svg)](https://cve.bz/cve/CVE-2016-0025)

HTML:

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

Affected

Versions

From the NVD's CPE matches.

ProductAffected
microsoft:office2010:sp2
microsoft:office2016
microsoft:office_web_apps2010:sp2
microsoft:office_web_apps_server2013:sp1
microsoft:sharepoint_server2010:sp2
microsoft:sharepoint_server2013:sp1
microsoft:word2007:sp3
microsoft:word2010:sp2
microsoft:word2013:sp1
microsoft:word2016
microsoft:word_for_mac2011
microsoft:word_for_mac2016

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON