dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 2 Sep 2025.
AccessApplication · Microsoft

CVE-2007-0671

HIGH · 8.8 CVSS v3.1 Published 2007-02-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is a 2007 zero-day vulnerability in Microsoft Excel (versions 2000, XP, 2003, and 2004 for Mac) that allowed arbitrary code execution through malicious Excel files. The attack vector is user-assisted, requiring the victim to open a specially crafted file. The vulnerability was exploited in targeted attacks using the Exploit-MSExcel.h proof-of-concept.

MitigationApply the relevant Microsoft security patches from that era (MS07-025 and subsequent Office updates) or upgrade to supported Office versions; enforce policies to prevent opening untrusted Excel attachments.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
AccessApplication
Affected:= 2000= 2002= 2003
ExcelApplication
Affected:= 2000= 2002= 2003
Excel ViewerApplication
Affected:= 2003
FrontpageApplication
Affected:= 2000= 2002= 2003
InfopathApplication
Affected:= 2003
OfficeApplication
Affected:= 2000= 2003= 2004= xp
OnenoteApplication
Affected:= 2003
OutlookApplication
Affected:= 2000= 2002= 2003

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Microsoft Office products
    Review the list of installed programs in your system settings or use a command to list installed software.
    Affected if You have any of the following products: Microsoft Access 2000, 2002, 2003; Microsoft Excel 2000, 2002, 2003; Microsoft Excel Viewer 2003; Microsoft Frontpage 2000, 2002, 2003; Microsoft Infopath 2003; Microsoft Office 2000, 2003, 2004, xp; Microsoft Onenote 2003; Microsoft Outlook 2000, 2002, 2003.
  2. Verify specific version numbers
    Compare your installed version numbers of the identified products against the affected version ranges.
    Affected if Your installed version matches any of the specified affected versions.
  3. Inspect for feature configurations
    Review the configuration settings of the installed Microsoft Office products to identify if any specific features that could be exploited are enabled.
    Affected if Any vulnerable features that could be exploited by remote user-assisted attackers are enabled.

You are affected if you have any of the specified Microsoft Office products in the listed versions and any vulnerable features enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the relevant Microsoft security patches from that era (MS07-025 and subsequent Office updates) or upgrade to supported Office versions; enforce policies to prevent opening untrusted Excel attachments.

Recommended fix Moderate confidence

Microsoft Office 2016 or later / Microsoft 365 (all affected versions listed are past end of support; no direct 'fixed version' exists for the legacy products themselves)

  1. Identify all systems running the affected Microsoft Office versions (Office 2000, XP, 2003, 2004, or component-specific versions like Excel 2000/2002/2003)
  2. Verify the exact version and patch level of Office installations using 'winver' or via Software Inventory
  3. Since this CVE relates to a zero-day exploit in Excel (CVE-2007-0671), locate and apply the relevant Microsoft security bulletin patch - historically this would have been addressed in MS07-002 or subsequent Office security updates
  4. If legacy systems cannot be patched, consider isolating them from untrusted network paths and disabling Excel file associations for unknown senders
  5. For systems where patch installation is not feasible, migrate data to supported Office versions (Office 2016/2019/365)
Caveat Legacy Office file formats and macros may require migration/adjustment; some third-party plugins/add-ins may be incompatible with newer Office versions; enterprise deployment planning recommended

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Access Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-0671 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-0671 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data