# CVE-2007-0671: Microsoft Office Excel Remote Code Execution

> Remote attackers can execute arbitrary code via malicious Excel files, requiring user interaction to open the document.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 12 Aug 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Feb 2007
- **Updated:** 12 Jan 2026
- **Also known as:** GHSA-h24h-phxr-rg3x

## What is CVE-2007-0671?

CVE-2007-0671 is a high-severity code injection vulnerability in Microsoft Excel, published on 3 Feb 2007. 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

Unspecified vulnerability in Microsoft Excel 2000, XP, 2003, and 2004 for Mac, and possibly other Office products, allows remote user-assisted attackers to execute arbitrary code via unknown attack vectors, as demonstrated by Exploit-MSExcel.h in targeted zero-day attacks.

## Which versions are affected by CVE-2007-0671?

It affects 14 products.


Products: Microsoft Access, Microsoft Excel, Microsoft Excel Viewer, Microsoft Frontpage, Microsoft Infopath, Microsoft Office, Microsoft Onenote, Microsoft Outlook, Microsoft Powerpoint, Microsoft Project, Microsoft Publisher, Microsoft Visio, Microsoft Word, Microsoft Word Viewer.

## How do I fix CVE-2007-0671?

No fix has been published for CVE-2007-0671 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 2 Sep 2025.

## Is CVE-2007-0671 being exploited?

Yes. Attackers have exploited CVE-2007-0671 in the wild since at least 12 Aug 2025.

## Other vulnerabilities in Microsoft Excel

- [CVE-2000-0788](https://insights.sbomify.com/CVE-2000-0788/): Code injection in n/a (critical 10.0)
- [CVE-2015-2503](https://insights.sbomify.com/CVE-2015-2503/): Security feature bypass in n/a (critical 9.3)
- [CVE-2013-3155](https://insights.sbomify.com/CVE-2013-3155/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-3156](https://insights.sbomify.com/CVE-2013-3156/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-3157](https://insights.sbomify.com/CVE-2013-3157/): Memory corruption in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-0671 and fix it if it is affected.

What it is: CVE-2007-0671 is a high-severity code injection vulnerability in Microsoft Excel, published on 3 Feb 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2007-0671 in the wild since at least 12 Aug 2025.

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-2007-0671/ (Markdown: https://insights.sbomify.com/CVE-2007-0671/index.md)
```

## Sources

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

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