CVE-2002-0619
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 · uneditedThe Mail Merge Tool in Microsoft Word 2002 for Windows, when Microsoft Access is present on a system, allows remote attackers to execute Visual Basic (VBA) scripts within a mail merge document that is saved in HTML format, aka a "Variant of MS00-071, Word Mail Merge Vulnerability" (CVE-2000-0788).
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 confidenceMicrosoft Word 2002's Mail Merge Tool, when Microsoft Access is installed on the system, allows execution of Visual Basic for Applications (VBA) scripts embedded within mail merge documents saved in HTML format. This enables remote attackers to achieve arbitrary code execution by tricking users into opening maliciously crafted Word documents.
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= xpCVSS 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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Verify Microsoft Office versionOpen Word, go to Help > About Microsoft Word. Alternatively, check Add/Remove Programs for Microsoft Office installation.Affected if Office version is 2000 or XP (Office xp)
-
Confirm Microsoft Access is installedCheck if Microsoft Access is present on the system by looking in the Office program group, checking Add/Remove Programs, or attempting to launch access.exe from the Office installation directory.Affected if Microsoft Access is installed on the same system as Word
-
Check for recent mail merge documents in HTML formatSearch the filesystem for .html or .htm files created from Word mail merge operations. Look in common document locations or check recent documents.Affected if User has opened or created mail merge documents saved in HTML format from untrusted sources
-
Verify VBA macro execution settingIn Word, go to Tools > Macro > Security to check the macro security level. Also check if macros from untrusted sources could execute.Affected if Macro security is set to Low or Medium, allowing VBA scripts to run automatically
User is affected if running Microsoft Office 2000 or XP with Microsoft Access installed, and they open maliciously crafted Word mail merge documents saved in HTML format from untrusted sources.
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.
From vendor dataApply the relevant Microsoft security update for Office XP, or disable VBA macros in Office applications, or remove Microsoft Access if unused. Users should not open untrusted Word documents from unknown sources.
- Consultation4.0 h
- Implementation2.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,624.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0619 — 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-2002-0619 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