CVE-2003-0114
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 file upload control in Microsoft Internet Explorer 5.01, 5.5, and 6.0 allows remote attackers to automatically upload files from the local system via a web page containing a script to upload the files.
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 confidenceMicrosoft Internet Explorer 5.01, 5.5, and 6.0 contains a file upload vulnerability where malicious web pages can use script to automatically trigger uploads of files from the user's local system without their knowledge or explicit interaction.
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.0= 5.0.1= 5.5= 6.0CVSS 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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 if Internet Explorer is installedLook for Internet Explorer in the Start Menu, or check for iexplore.exe in common paths such as C:\Program Files\Internet Explorer\iexplore.exe or C:\Program Files (x86)\Internet Explorer\iexplore.exeAffected if Internet Explorer executable exists on the system
-
Determine the installed Internet Explorer versionOpen Internet Explorer, then go to Help > About Internet Explorer, or run 'reg query "HKLM\SOFTWARE\Microsoft\Internet Explorer" /v Version' in Command PromptAffected if The reported version is 5.0.1, 5.5, or 6.0
-
Verify the underlying MSHTML component versionRun 'reg query "HKLM\SOFTWARE\Microsoft\Internet Explorer" /v Build' or check the file version of mshtml.dll in C:\Windows\System32 (or C:\Windows\SysWOW64 on 64-bit systems)Affected if The build number matches the vulnerable IE versions 5.0.1, 5.5, or 6.0
If Internet Explorer versions 5.0.1, 5.5, or 6.0 are installed and in use, the system is affected by this file upload vulnerability.
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 dataUsers should immediately stop using the affected end-of-life Internet Explorer versions and migrate to a supported modern web browser (Microsoft Edge, Chrome, Firefox) or apply available Microsoft security patches if they must continue using legacy browsers.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2003-0114 — 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-0114 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