CVE-2015-6093 — Microsoft Office 2007 SP3, Office 2010 SP2, Office 2013 SP1, Office 2013 RT SP1, Office 2016,...
Microsoft Office 2007 SP3, Office 2010 SP2, Office 2013 SP1, Office 2013 RT SP1, Office 2016, Word Automation Services on SharePoint Server 2010 SP2 and 2013 SP1, Office Web Apps 2010 SP2, and Office Web Apps Server 2013 SP1 allow remote attackers to execute arbitrary code via a crafted Office document, aka "Microsoft Office Memory Corruption Vulnerability."
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 23.2% (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.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
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 Office, Microsoft Office Web Apps, Microsoft Office Web Apps Server…).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- EPSS ahead of 98% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Microsoft | Office | version 2007-sp3version 2010-sp2version 2013-sp1version 2016 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Office Web Apps | version 2010-sp2 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Office Web Apps Server | version 2013-sp1 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Sharepoint Server | version 2010-sp2version 2013-sp1 | 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 |
|---|---|---|---|---|---|
| 9.3 | CVSS 2.0 | High | 8.6 | 10.0 | nvd@nist.gov via NIST National Vulnerability Database |
AV:N/AC:M/Au:N/C:C/I:C/A:C (score shown at the top: nvd@nist.gov) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CWE-119 · Buffer Errors (Improper Restriction of Operations within Memory Bounds)
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Record published
- Affected products added · microsoft/office, microsoft/office web apps, microsoft/office web apps server, microsoft/sharepoint server
- CVSS changed · 9.3
- Source status changed · → Modified
- Record created in this database
- 2015
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 14, 2026 – Oct 14, 2026
- 1× Official description updated · Oct 14, 2026 – Oct 14, 2026
References
7 on the record
- www.securitytracker.com/id/1034122
- www.securityfocus.com/bid/77491
- www.securitytracker.com/id/1034118
- github.com/advisories/GHSA-v28g-cwg8-jqvp
- docs.microsoft.com/en-us/security-updates/securitybulletins/2015/ms15-116
- www.zerodayinitiative.com/advisories/ZDI-15-539
- nvd.nist.gov/vuln/detail/CVE-2015-6093
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-97783 Microsoft Office SharePoint Spoofing Vulnerability 2d
- Medium CVE-2026-97782 Microsoft Office SharePoint Tampering Vulnerability 2d
- High CVE-2026-97755 Microsoft Office Excel Remote Code Execution Vulnerability 2d
- High CVE-2026-96044 Microsoft Office SharePoint Elevation of Privilege Vulnerability 2d
- High CVE-2026-88206 Microsoft Office SharePoint Elevation of Privilege Vulnerability 2d
- Medium CVE-2026-88208 Microsoft Office SharePoint Spoofing 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 fixed version, patch or mitigation documented.
- 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-2015-6093 is "Microsoft Office 2007 SP3, Office 2010 SP2, Office 2013 SP1, Office 2013 RT SP1, Office 2016,...", rated High. It affects Office (Microsoft); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 9.3 describes technical severity. EPSS 23.20% 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.