CVE-2007-0515
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 · uneditedUnspecified vulnerability in Microsoft Word allows user-assisted remote attackers to execute arbitrary code on Word 2000, and cause a denial of service on Word 2003, via unknown attack vectors that trigger memory corruption, as exploited by Trojan.Mdropper.W and later by Trojan.Mdropper.X, a different issue than CVE-2006-6456, CVE-2006-5994, and CVE-2006-6561.
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 confidenceMemory corruption vulnerability in Microsoft Word 2000 and 2003 that allows remote code execution (Word 2000) or denial of service (Word 2003) via user-assisted opening of malicious Word documents. Exploited by Trojan.Mdropper.W and Trojan.Mdropper.X malware families.
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= 2000= 2003= 2004= xp= 2000= 2002= 2003= 2003= 2004= 2005= 2006CVSS 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
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Microsoft Word versionOpen Word, go to Help > About Microsoft Office Word, or check Add/Remove Programs for Microsoft Office installationAffected if Version is 2000, 2002 (XP), or 2003 without corresponding security patch MS07-014 installed
-
Check for security patch MS07-014Open Control Panel > Add or Remove Programs, enable 'Show updates', search for 'MS07-014' or 'Security Update for Microsoft Office' (released January 2007). Alternatively, run: wmic qfe list | findstr /i "KB929760"Affected if Patch KB929760 (MS07-014) is NOT listed among installed updates
-
Verify Microsoft Word Viewer version if installedCheck Add/Remove Programs for Microsoft Word Viewer 2003, or open Word Viewer and check Help > AboutAffected if Word Viewer 2003 is installed without security patch MS07-014 applied
-
Confirm Microsoft Works version if installedCheck Add/Remove Programs for Microsoft Works (versions 2004, 2005, or 2006)Affected if Microsoft Works 2004, 2005, or 2006 is installed and the associated security update is not applied
-
Check Microsoft Office suite version if Word is bundledOpen any Office application, go to Help > About, or check Add/Remove Programs for Microsoft Office (versions 2000, 2003, 2004, or XP)Affected if Office suite version matches affected list and patch MS07-014 is missing from Windows Update history
User is affected if Microsoft Word 2000/2002/2003, Word Viewer 2003, or Microsoft Works 2004-2006 is installed AND security patch MS07-014 (KB929760) is not installed.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply Microsoft security patches for CVE-2007-0515 (released circa January 2007). Until patched, disable active content in Word, use Protected View, and avoid opening untrusted .doc files.
Microsoft Security Bulletin MS07-014 (specific patch for each affected product)
- Check the Microsoft Security Bulletin MS07-014 for this vulnerability (Windows Word 2000 Security Update, Windows Word 2002 Security Update, Windows Word 2003 Security Update)
- Download the appropriate security update from Microsoft Update or the Microsoft Download Center
- Apply the security update to all affected systems
- Verify the update was installed successfully via Add/Remove Programs or the version number in Word's About dialog
- Restart Word and confirm normal operation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0515 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-0515 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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