CVE-2017-0281 — Microsoft Office 2007 SP3, Office 2010 SP2, Office 2013 SP1, Office 2016, Office Online Server...
Microsoft Office 2007 SP3, Office 2010 SP2, Office 2013 SP1, Office 2016, Office Online Server 2016, Office Web Apps 2010 SP2,Office Web Apps 2013 SP1, Project Server 2013 SP1, SharePoint Enterprise Server 2013 SP1, SharePoint Enterprise Server 2016, SharePoint Foundation 2013 SP1, Sharepoint Server 2010 SP2, Word 2016, and Skype for Business 2016 allow a remote code execution vulnerability when the software fails to properly handle objects in memory, aka "Office Remote Code Execution Vulnerability". This CVE ID is unique from CVE-2017-0261 and CVE-2017-0262.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 15.8% (30-day exploitation probability)+15
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — portal.msrc.microsoft.com (NIST National Vulnerability Database)
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Microsoft Microsoft SharePoint Foundation, Microsoft Office, Microsoft Office Online Server…).
- Apply the fixed version or the patch documented under Remediation.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- EPSS ahead of 97% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Microsoft | Microsoft SharePoint Foundation | version 2013-sp1 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Office | version 2007-sp3version 2010-sp2version 2013-sp1version 2016 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Office | version Microsoft Office 2007 SP3, Office 2010 SP2, Office 2013 SP1, Office 2016, Office | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Microsoft | Office Online Server | version 2016 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Office Web Apps | version 2010-sp2version 2013-sp1 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Project Server | version 2013-sp1 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Sharepoint Server | version 2010-sp2version 2013-sp1version 2016 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Skype For Business | version 2016 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Word | version 2016 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.0 | High | 1.8 | 5.9 | nvd@nist.gov via NIST National Vulnerability Database |
| 7.8 | CVSS 3.0 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 9.3 | CVSS 2.0 | High | 8.6 | 10.0 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov) Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · microsoft corporation/microsoft office
- SSVC assessment updated
- Record published
- Fix documented
- Affected products added · microsoft/office, microsoft/office online server, microsoft/office web apps, microsoft/project server, microsoft/sharepo
- CVSS changed · 7.8
- Source status changed · → Modified
- Record created in this database
- 2017
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 15, 2026 – Oct 15, 2026
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
4 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-108446 Microsoft Office Excel Remote Code Execution Vulnerability 2h
- Medium CVE-2026-97783 Microsoft Office SharePoint Spoofing Vulnerability 2d
- High CVE-2026-97780 Microsoft Office Excel Remote Code Execution Vulnerability 2d
- Medium CVE-2026-97782 Microsoft Office SharePoint Tampering Vulnerability 2d
- High CVE-2026-97772 Microsoft Office Excel Remote Code Execution Vulnerability 2d
- High CVE-2026-97776 Microsoft Office Excel Remote Code Execution Vulnerability 2d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No CWE classification.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2017-0281 is "Microsoft Office 2007 SP3, Office 2010 SP2, Office 2013 SP1, Office 2016, Office Online Server...", rated High. It affects Microsoft SharePoint Foundation (Microsoft); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 15.76% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.