CVE-2013-0007
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 XML Core Services (aka MSXML) 4.0, 5.0, and 6.0 does not properly parse XML content, which allows remote attackers to execute arbitrary code via a crafted web page, aka "MSXML XSLT 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 confidenceMicrosoft XML Core Services (MSXML) versions 4.0, 5.0, and 6.0 contain a memory corruption vulnerability in their XML and XSLT parsing logic. By tricking a user into visiting a specially crafted web page, attackers can trigger improper parsing that leads to arbitrary code execution with the victim'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= 3.0= 4.0= 6.0= 5.0all versionsall versionsall versionsall versions= r2all versionsall versionsall versionsCVSS 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 MSXML versionsCheck the Windows registry under HKLM\SOFTWARE\Microsoft\MSXML for installed MSXML versions (look for keys like MSXML3, MSXML4, MSXML5, MSXML6), or search for msxml3.dll, msxml4.dll, msxml5.dll, msxml6.dll files in system directories and check their file versionsAffected if Any MSXML version 3.0, 4.0, 5.0, or 6.0 is installed on a supported Windows version (XP, Vista, 7, 8, Server 2003, 2008, 2008 R2, 2012)
-
Confirm the specific MSXML version numberOpen the file properties of the found msxml*.dll file to verify the exact version (for example, msxml6.dll version 6.20.XXXX.0 or similar)Affected if The installed MSXML version matches 3.0, 4.0, 5.0, or 6.0 specifically
-
Check if Internet Explorer active scripting is enabledIn Internet Explorer, go to Internet Options > Security > Custom Level > Script ActiveX controls marked safe for scripting, or check the registry value under HKCU\Software\Microsoft\Windows\CurrentVersion\Internet Settings\ZonesAffected if Active scripting is enabled in Internet Explorer, allowing web pages to execute script that could trigger the vulnerable MSXML parsing code
-
Identify applications using MSXMLReview installed software that may leverage MSXML for XML processing, such as Microsoft Office components, Internet Explorer, or third-party applications that depend on MSXML librariesAffected if Any application on the system uses the vulnerable MSXML library for XML or XSLT parsing
A system is affected if it has MSXML version 3.0, 4.0, 5.0, or 6.0 installed on a vulnerable Windows version and the MSXML component can be invoked through web-based content or applications that process untrusted XML/XSLT input.
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 (MS13-002) to patch the vulnerable MSXML versions, or disable active scripting in Internet Explorer as a temporary workaround.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0007 — 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-0007 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