CVE-2013-0082
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 · uneditedMicrosoft Office 2003 SP3 and 2007 SP3 allows remote attackers to execute arbitrary code via a crafted WordPerfect document (.wpd) file, aka "WPD File Format Memory Corruption 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 · moderate confidenceMemory corruption vulnerability in Microsoft Office's parser for WordPerfect documents (.wpd). When processing a specially crafted .wpd file, the application fails to properly handle memory operations, allowing an attacker to overwrite memory and execute arbitrary code with the current 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= 2007CVSS 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.
-
Check installed Microsoft Office versionOpen Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Office\{version}\Common\InstallRoot, or run `winword /?` from Command Prompt to display the version, or right-click WINWORD.EXE in Program Files and select PropertiesAffected if Version is 2003 or 2007 (exact match to affected versions)
-
Confirm WordPerfect document converter componentCheck for the presence of WPCONVRT.DLL or WPFT.CNV in the Office common files directory (typically C:\Program Files\Microsoft Office\Office{version})Affected if The WordPerfect converter DLL exists and is loaded by Office applications when opening .wpd files
-
Verify .wpd file handler associationCheck registry key HKCR\.wpd to confirm WordPerfect documents are associated with Microsoft Office convertersAffected if Office is set as the default handler for .wpd files, enabling automatic parsing upon file opening
-
Detect recent .wpd file activityReview Windows Event Viewer for recent .wpd file opens, or check user Recent Documents folder for .wpd filesAffected if Users have opened or attempted to open WordPerfect documents, triggering the vulnerable parser code path
Your environment is affected if Microsoft Office 2003 or 2007 is installed AND the WordPerfect document converter is enabled, allowing .wpd files to be parsed by the vulnerable code path.
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 update MS13-024 (or subsequent superseded bulletin) to patch the vulnerability. Until patched, instruct users to avoid opening untrusted or unexpected WordPerfect document files received via email or downloaded from untrusted sources.
Microsoft Office 2010 or later (Office 365 recommended for continuous security updates)
- Upgrade Microsoft Office to a supported version (Office 2010 or later, with Office 365 recommended for latest security updates)
- After upgrading, verify that the new Office version properly handles .wpd files or consider using alternative document conversion tools
- Ensure antivirus/anti-malware solutions are current and scan any .wpd files before opening
- Implement user training to avoid opening untrusted .wpd files from unknown sources
- Consider blocking .wpd file attachments at the email gateway as a defense-in-depth measure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0082 — 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-2013-0082 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