CVE-2004-1133
Overview
CVE-2004-1133 is a known-severity vulnerability affecting microsoft w3who.dll. It was published on January 10, 2005.
Technical Description
Multiple cross-site scripting (XSS) vulnerabilities in Microsoft W3Who ISAPI (w3who.dll) allow remote attackers to inject arbitrary HTML and web script via (1) HTTP headers such as "Connection" or (2) invalid parameters whose values are echoed in the resulting error message.
Remediation
Check the references section for vendor advisories and patches from microsoft. Update w3who.dll to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
Affected Products
| Vendor | Product | Versions | Status |
|---|
References
Frequently Asked Questions
What is CVE-2004-1133?
CVE-2004-1133 is a known-severity vulnerability affecting microsoft w3who.dll. It was published on January 10, 2005.
How severe is CVE-2004-1133?
CVSS score information is not yet available for this vulnerability. Check back as the CVE record is updated by NVD analysts.
How do I fix or remediate CVE-2004-1133?
Check the references section for vendor advisories and patches from microsoft. Update w3who.dll to the latest patched version. If immediate patching is not possible, review the CVSS vector to understand the attack surface and apply compensating controls such as network segmentation or access restrictions.
How can CyberStrike help with CVE-2004-1133?
CyberStrike's AI-powered security agents can automatically detect CVE-2004-1133 across your infrastructure using autonomous pentesting, DAST scanning, and HackBrowser. The platform continuously monitors for known vulnerabilities and provides actionable remediation guidance prioritized by real-world exploitability.
How CyberStrike Helps
AI agents map your attack surface to find vulnerabilities like this one.
Automated penetration testing that runs continuously, not just quarterly.
AI-driven PR review catches vulnerable dependencies before they ship.
Browser-based exploitation validates findings with real proof-of-concept.