CVE Intelligence
Medium Info disclosure

CVE-2015-2423 — Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8,...

Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT Gold and 8.1, Windows 10, Excel 2007 SP3, PowerPoint 2007 SP3, Visio 2007 SP3, Word 2007 SP3, Office 2010 SP2, Excel 2010 SP2, PowerPoint 2010 SP2, Visio 2010 SP2, Word 2010 SP2, Excel 2013 SP1, PowerPoint 2013 SP1, Visio 2013 SP1, Word 2013 SP1, Excel 2013 RT SP1, PowerPoint 2013 RT SP1, Visio 2013 RT SP1, Word 2013 RT SP1, and Internet Explorer 7 through 11 allow remote attackers to gain privileges and obtain sensitive information via a crafted command-line parameter to an Office application or Notepad, as demonstrated by a transition from Low Integrity to Medium Integrity, aka "Unsafe Command Line Parameter Passing Vulnerability."

Published Aug 14, 2015 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: microsoft

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 19.9% (30-day exploitation probability)+15
  • Technical severity (medium)+3

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.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
19.85%
ahead of 97% of scored CVEs · Oct 14, 2026
Affects
Microsoft
Excel and 14 more
CVSS base
4.3
Medium · 1 source(s)

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.

Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original 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.

  1. Identify exposed assets running the affected vendor/product/version combinations (Microsoft Excel, Microsoft Internet Explorer, Microsoft Office…).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. EPSS ahead of 97% of scored CVEs: prioritize it in the patch queue.
  5. Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Microsoft Excel version 2013-sp1version 2010-sp2version 2007-sp3 Vulnerable NIST National Vulnerability Database
Microsoft Internet Explorer version 11version 10version 9version 7version 8 Vulnerable NIST National Vulnerability Database
Microsoft Office version 2010-sp2 Vulnerable NIST National Vulnerability Database
Microsoft Powerpoint version 2007-sp3version 2010-sp2version 2013-sp1 Vulnerable NIST National Vulnerability Database
Microsoft Visio version 2007-sp3version 2010-sp2version 2013-sp1version 2016 Vulnerable NIST National Vulnerability Database
Microsoft Windows 10 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows 7 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows 8 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows 8.1 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows Rt versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows Rt 8.1 versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2008 version r2-sp1versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows Server 2012 version r2versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Windows Vista versions not specified by the source Vulnerable NIST National Vulnerability Database
Microsoft Word version 2007-sp3version 2010-sp2version 2013-sp1version 2016 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Medium
Authentication
None
Confidentiality
Partial
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
4.3 CVSS 2.0 Medium 8.6 2.9 nvd@nist.gov via NIST National Vulnerability Database
AV:N/AC:M/Au:N/C:P/I:N/A:N (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-200 · Exposure of Sensitive Information

Other CVEs with this weakness →

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).
  • Look for anomalous data read/export volumes and access to sensitive records.
web/proxy/WAF logsnetwork IDS/IPSapplication logsauthentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 14, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 14, 2026
  • Fix documented
    Oct 14, 2026 · NIST National Vulnerability Database
  • Affected products added · microsoft/excel, microsoft/office, microsoft/powerpoint, microsoft/visio, microsoft/word, microsoft/internet explorer, m
    Oct 14, 2026 · NIST National Vulnerability Database
  • CVSS changed · 4.3
    Oct 14, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 14, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 14, 2026 · Alertas do Telegram
  • 2015
  • CVE published
    Aug 14, 2015 · microsoft

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

8 on the record

Elsewhere on this site

Microsoft
every CVE for this vendor
Info disclosure
same class
CWE-200
other pages naming this weakness

Related CVEs (same products)

  • Medium CVE-2026-97844 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97843 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97839 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97840 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97842 Role: DNS Server Information Disclosure Vulnerability 2d
  • Medium CVE-2026-97841 Role: DNS Server Information Disclosure 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 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-2423 is "Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8,...", rated Medium. It affects Excel (Microsoft); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.3 describes technical severity. EPSS 19.85% 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.