CVE-2003-1107
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 DHTML capability in Microsoft Windows Media Player (WMP) 6.4, 7.0, 7.1, and 9 may run certain URL commands from a security zone that is less trusted than the current zone, which allows attackers to bypass intended access restrictions.
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 confidenceWindows Media Player versions 6.4, 7.0, 7.1, and 9 contain a DHTML capability that improperly executes URL commands from a security zone that is less trusted than the user's current zone, allowing attackers to bypass intended zone-based access restrictions.
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= 6.4= 7= 7.1= 9CVSS 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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/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.
-
Confirm Windows Media Player is installedLocate wmp.dll in the Windows System directory (e.g., C:\Windows\System32\wmp.dll) or check for the Windows Media Player program in Start MenuAffected if wmp.dll exists or WMP program is present on the system
-
Retrieve Windows Media Player version numberRight-click wmp.dll, select Properties, and view the Version tab to read the File Version; alternatively, open WMP, go to Help > About Windows Media PlayerAffected if Version displayed is 6.4, 7.0, 7.1, or 9.x
-
Verify exact version matches affected rangeCompare the obtained version against the known affected list: 6.4, 7, 7.1, and 9Affected if Installed version is exactly 6.4, 7.0, 7.1, or 9.x (any subversion of 9)
-
Confirm DHTML feature is enabledCheck Windows Media Player settings or browser integration settings where DHTML scripting capabilities may be permitted; in registry, verify HKCU\Software\Microsoft\MediaPlayer\Preferences\EnableDHTML is not set to 0 or disabledAffected if DHTML functionality is available and not explicitly disabled
User is affected if Windows Media Player version 6.4, 7.0, 7.1, or 9.x is installed with DHTML capability enabled on the system.
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 available Microsoft security patches for Windows Media Player or upgrade to a patched version. If patches are unavailable for these legacy versions (2003 era), implement compensating controls such as restricting WMP file types at the proxy/gateway level or disabling the DHTML functionality via registry settings.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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 $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2003-1107 — 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-2003-1107 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