CVE-2007-0216
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 · uneditedwkcvqd01.dll in Microsoft Works 6 File Converter, as used in Office 2003 SP2, Works 8.0, and Works Suite 2005, allows remote attackers to execute arbitrary code via a .wps file with crafted section length headers, aka "Microsoft Works File Converter Input Validation Vulnerability."
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 confidenceA buffer overflow vulnerability exists in wkcvqd01.dll, the Microsoft Works 6 File Converter, due to improper input validation of section length headers in .wps files. When a user opens a specially crafted malicious .wps file, the converter fails to validate the section length properly before copying data into a fixed-size buffer, allowing attackers to overwrite execution flow and achieve remote code execution with the user's privileges.
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= 2003= 8.0= 2005CVSS 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.
-
Confirm Office 2003 or Works installationCheck installed programs in Control Panel or run 'wmic product get name,version' to list installed Microsoft Office and Works versionsAffected if Microsoft Office 2003, Works 8.0, or Works Suite 2005 is present on the system
-
Locate the vulnerable DLLSearch for wkcvqd01.dll on the system - typical locations include C:\Program Files\Common Files\Microsoft Shared\TextConv or within Office 2003 directory structuresAffected if The file wkcvqd01.dll exists on the system
-
Verify .wps file handler registrationCheck Windows registry under HKCR\.wps or HKLM\SOFTWARE\Classes\.wps to see which application handles .wps file opensAffected if The system is configured to open .wps files using the Microsoft Works converter
-
Review recent .wps file accessCheck Windows Event Viewer, prefetch files, or recent documents for evidence of .wps file openings, or inspect email gateway logs for .wps attachmentsAffected if Users have recently opened .wps files from untrusted sources
A system is likely affected if it has Office 2003, Works 8.0, or Works Suite 2005 installed with the wkcvqd01.dll converter present and users who could open malicious .wps files.
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 Microsoft security update KB925256 (or subsequent superseded patch) to address the vulnerable wkcvqd01.dll component in affected Office 2003 SP2, Works 8.0, and Works Suite 2005 installations; consider blocking or warning on untrusted .wps file attachments at the email gateway as an additional defense-in-depth measure.
- Consultation3.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,304.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0216 — 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-0216 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