# CVE-2015-2423: Privilege escalation in n/a

> Attackers can escalate privileges and read sensitive data by tricking users into opening crafted files in Office or Notepad.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Aug 2015
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-w76h-498m-3wj9

## What is CVE-2015-2423?

CVE-2015-2423 is a medium-severity vulnerability in Microsoft Excel, published on 15 Aug 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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."

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2015-2423?

It affects 15 products.


Products: Microsoft Excel, Microsoft Internet Explorer, Microsoft Office, Microsoft Powerpoint, Microsoft Visio, Microsoft Windows 10, Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 8.1, Microsoft Windows Rt, Microsoft Windows Rt 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Vista, Microsoft Word.

## How do I fix CVE-2015-2423?

No fix has been published for CVE-2015-2423 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-2423 being exploited?

There is no known exploitation of CVE-2015-2423 in the wild and no public exploit code.

## Other vulnerabilities in Microsoft Excel

- [CVE-2019-1297](https://insights.sbomify.com/CVE-2019-1297/): Microsoft Excel Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2009-0238](https://insights.sbomify.com/CVE-2009-0238/): Microsoft Office Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2016-7262](https://insights.sbomify.com/CVE-2016-7262/): Microsoft Office Security Feature Bypass (high 7.8, exploited in the wild)
- [CVE-2009-3129](https://insights.sbomify.com/CVE-2009-3129/): Microsoft Excel Featheader Record Memory Corruption (high 7.8, exploited in the wild)
- [CVE-2008-0081](https://insights.sbomify.com/CVE-2008-0081/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-2423 and fix it if it is affected.

What it is: CVE-2015-2423 is a medium-severity vulnerability in Microsoft Excel, published on 15 Aug 2015. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-2423 in the wild and no public exploit code.

Affected product: Microsoft Excel. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-2423/ (Markdown: https://insights.sbomify.com/CVE-2015-2423/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-2423
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-2423
- OSV: https://osv.dev/vulnerability/CVE-2015-2423

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-2423/
Summaries are generated and may contain mistakes; the official description above is the record.