CVE-2007-0671 — Microsoft Office Excel Remote Code Execution Vulnerability
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.
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
- Confirmed exploitation (CISA KEV)+35
- EPSS 43.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.
CISA required action CISA
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
US federal deadline: Sep 2, 2025 — passed 408 day(s) ago
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 Access, Microsoft Excel, Microsoft Excel Viewer…).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- 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.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- EPSS ahead of 99% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Microsoft | Access | version 2003version 2002version 2000 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Excel | version 2002version 2003version 2000 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Excel Viewer | version 2003 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Frontpage | version 2003version 2002version 2000 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Infopath | version 2003 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Office | version xp-sp3version 2004version 2003-sp2version 2000-sp3 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Onenote | version 2003 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Outlook | version 2000version 2002version 2003 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Powerpoint | version 2002version 2000version 2003 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Project | version 2000-sr1version 2003version 2002-sp1 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Publisher | version 2000version 2002version 2003 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Visio | version 2002-sp2version 2003 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Word | version 2000version 2002version 2003 | Vulnerable | NIST National Vulnerability Database |
| Microsoft | Word Viewer | version 2003 | 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 |
|---|---|---|---|---|---|
| 8.8 | CVSS 3.1 | High | 2.8 | 5.9 | 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database |
| 8.8 | CVSS 3.1 | High | — | — | GitHub, Inc. via GitHub Security Advisories |
| 8.8 | CVSS 3.1 | High | — | — | CISA-ADP via CVE Program (cve.org) e CISA ADP |
| 9.3 | CVSS 2.0 | High | 8.6 | 10.0 | nvd@nist.gov via NIST National Vulnerability Database |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: 134c704f-9b21-4f2e-91b3-4a467353bcc0) CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
EPSS over time FIRST
Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 43.24%
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).
- Hunt retroactively in logs from before Aug 12, 2025 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- SSVC assessment updated
- Record published
- Affected products added · microsoft/access, microsoft/excel, microsoft/excel viewer, microsoft/frontpage, microsoft/infopath, microsoft/office, mi
- CVSS changed · 8.8
- Source status changed · → Analyzed
- Added to CISA KEV (detected)
- Record created in this database
- 2025
- Added to CISA KEV catalog
- 2007
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
17 on the record
- www.vupen.com/english/advisories/2007/0463
- learn.microsoft.com/en-us/security-updates/securitybulletins/2007/ms07-015
- www.microsoft.com/technet/security/advisory/932553.mspx
- docs.microsoft.com/en-us/security-updates/securitybulletins/2007/ms07-015
- secunia.com/advisories/24008
- www.kb.cert.org/vuls/id/613740
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- www.us-cert.gov/cas/techalerts/TA07-044A.html
- vil.nai.com/vil/content/v_141393.htm
- github.com/advisories/GHSA-h24h-phxr-rg3x
- nvd.nist.gov/vuln/detail/CVE-2007-0671
- osvdb.org/31901
- oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A301
- securitytracker.com/id
- www.securityfocus.com/bid/22383
- exchange.xforce.ibmcloud.com/vulnerabilities/32178
- www.avertlabs.com/research/blog/
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-70327 Out-of-bounds Read in Microsoft 365 Apps Aug 11, 2026
- Medium CVE-2026-70328 Out-of-bounds Read in Microsoft 365 Apps Aug 11, 2026
- High CVE-2026-70329 Integer Overflow or Wraparound in Microsoft 365 Apps Aug 11, 2026
- Medium CVE-2026-70318 Improper Input Validation in Microsoft 365 Apps Aug 11, 2026
- Medium CVE-2026-70310 Out-of-bounds Read in Microsoft 365 Apps Aug 11, 2026
- High CVE-2026-70311 Use After Free in Microsoft 365 Apps Aug 11, 2026
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 CWE classification.
- 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-2007-0671 is "Microsoft Office Excel Remote Code Execution Vulnerability", rated High. It affects Access (Microsoft); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 8.8 describes technical severity. EPSS 43.24% 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.