CVE-2015-1760 in the critical feed json
Microsoft Office Compatibility Pack SP3, Office 2010 SP2, Office 2013 SP1, and Office 2013 RT SP1 allow remote attackers to execute arbitra…
published 11y ago modified 4mo ago also EUVD-2015-1890
- cvss
- 9.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 16.3%
- EPSS 16.3% chance of exploitation in 30 days, percentile 96%
- public exploits
- 0
- none known
Summary
Microsoft Office Compatibility Pack SP3, Office 2010 SP2, Office 2013 SP1, and Office 2013 RT SP1 allow remote attackers to execute arbitrary code via a crafted Office document, aka "Microsoft Office Memory Corruption Vulnerability."
Is CVE-2015-1760 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
16.30% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 9.3 | AV:N/AC:M/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-19 Data Processing Errors
References
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2015/ms15-059
vendor-advisory
-
securitytracker.com
/id/1032523
vdb-entry
-
securityfocus.com
/bid/75015
vdb-entry
Sources
- CVE List CVE-2015-1760
- NVD CVE-2015-1760
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.