How severe is CVE-2007-0671?

CVE-2007-0671 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2007-0671?

Affected package information for CVE-2007-0671 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2007-0671?

No fixed version has been published for CVE-2007-0671 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2007-0671 actively exploited in the wild?

No public exploit code has been indexed for CVE-2007-0671 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2007-0671?

CVE-2007-0671 has an EPSS (Exploit Prediction Scoring System) score of 52.3%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2007-0671 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2007-0671 (Microsoft Office Excel Remote Code Execution Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2025-08-12. CISA required all US federal civilian agencies to remediate this vulnerability by 2025-09-02. The required action was: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

Which products and versions are affected by CVE-2007-0671?

CVE-2007-0671 affects microsoft access (3 versions, e.g. 2000, 2002, 2003); microsoft excel (3 versions, e.g. 2000, 2002, 2003); microsoft excel viewer (1 version, e.g. 2003); microsoft frontpage (3 versions, e.g. 2000, 2002, 2003), and 10 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2007-0671 published, and has it been updated?

CVE-2007-0671 was published on February 3, 2007 and was last updated on April 22, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2007-0671: ACCESS Remote Code Execution (High 8.8)

EPSS Exploitation Probability

via FIRST.org ↗

52.3%probability of exploitation in next 30 days

High Risk98th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

Affected Products

14 products · 34 configurations

Application

accessmicrosoft

3 versions

200020022003

Application

excelmicrosoft

3 versions

200020022003

Application

excel viewermicrosoft

1 version

2003

Application

frontpagemicrosoft

3 versions

200020022003

Application

infopathmicrosoft

1 version

2003

Application

officemicrosoft

4 versions

200020032004xp

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2007-0671 in your stack?

O3 detects CVE-2007-0671 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works