CVE-2003-0664
Microsoft Word 2002, 2000, 97, and 98(J) does not properly check certain properties of a document...
Microsoft Word 2002, 2000, 97, and 98(J) does not properly check certain properties of a document, which allows attackers to bypass the macro security model and automatically execute arbitrary macros via a malicious document.
Exploit likelihood
What each source reports
NVD Score used
Microsoft Word 2002, 2000, 97, and 98(J) does not properly check certain properties of a document, which allows attackers to bypass the macro security model and automatically execute arbitrary macros via a malicious document.
- Record
CVE-2003-0664- CVSS 2.0
- 7.5 High
AV:N/AC:L/Au:N/C:P/I:P/A:P - Updated
- 2026-11-02
CVE List No score
Microsoft Word 2002, 2000, 97, and 98(J) does not properly check certain properties of a document, which allows attackers to bypass the macro security model and automatically execute arbitrary macros via a malicious document.
- Record
CVE-2003-0664- Updated
- 2026-11-02
EUVDEUVD-2003-0658 No score
Microsoft Word 2002, 2000, 97, and 98(J) does not properly check certain properties of a document, which allows attackers to bypass the macro security model and automatically execute arbitrary macros via a malicious document.
- Record
EUVD-2003-0658- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-vpf6-wrhg-p4jg No score
Microsoft Word 2002, 2000, 97, and 98(J) does not properly check certain properties of a document...
Microsoft Word 2002, 2000, 97, and 98(J) does not properly check certain properties of a document, which allows attackers to bypass the macro security model and automatically execute arbitrary macros via a malicious document.
- Record
GHSA-vpf6-wrhg-p4jg- Updated
- 2026-11-02
Affected products
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2003-0664 is a high vulnerability (CVSS 7.5) in Microsoft Word, published September 4, 2003. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 4.13%, the 90th percentile. No source names a fixed version.