CVE-2005-1790

LOWCVSS v2 · 2.62.6—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 2.6 — v2 rates that LOW (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:H/Au:N/C:N/I:N/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 83.5% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
2.6EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 83%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 83%CVSS v2: 2.6Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Microsoft Internet Explorer 6 SP2 6.0.2900.2180 and 6.0.2800.1106, and earlier versions, allows remote attackers to cause a denial of service (crash) and execute arbitrary code via a Javascript BODY onload event that calls the window function, aka "Mismatched Document Object Model Objects Memory Corruption Vulnerability."

CVSS v2.0 (legacy)
2.6LOWNVD never assigned a CVSS v3 rating to this CVE
EG Score
2.6(low)
EG Risk
50(Track)
EG Risk 50/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity26% × 45%
Exploitation83% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
83%
EPSS %ILE
100%
KEV
Not listed

Published

June 1, 2005

Last Modified

April 16, 2026

References (48)

Data Freshness Timeline

(refreshed 2× in last 7d / 2× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-10 09:23 UTCEPSS rescore
  2. 2026-09-04 04:59 UTCEPSS rescore
  3. 2026-08-05 19:11 UTCEPSS rescore
  4. 2026-07-26 13:26 UTCEG score recompute▲ 2.60
  5. 2026-07-24 14:11 UTCEPSS rescore
  6. 2026-07-23 00:48 UTCEG score recompute
  7. 2026-07-23 00:28 UTCEG score recompute▼ 8.70
  8. 2026-07-22 23:52 UTCEG score recompute▲ 8.70
  9. 2026-07-22 21:32 UTCEG score recompute
  10. 2026-07-13 06:07 UTCEPSS rescore
  11. 2026-07-13 06:07 UTCEPSS rescore
  12. 2026-07-06 02:19 UTCEPSS rescore
  13. 2026-07-06 02:19 UTCEPSS rescore
  14. 2026-07-02 14:00 UTCEPSS rescore
  15. 2026-06-28 04:52 UTCEPSS rescore
  16. 2026-06-25 13:46 UTCEPSS rescore
  17. 2026-06-24 14:01 UTCEPSS rescore
  18. 2026-06-23 21:29 UTCEPSS rescore
  19. 2026-06-18 17:49 UTCEPSS rescore
  20. 2026-06-18 17:49 UTCEPSS rescore
  21. 2026-06-17 17:49 UTCEPSS rescore
  22. 2026-06-17 17:49 UTCEPSS rescore
  23. 2026-06-15 17:44 UTCEPSS rescore
  24. 2026-06-12 23:08 UTCEPSS rescore
  25. 2026-06-11 13:55 UTCEPSS rescore
Show 29 more
  1. 2026-06-10 22:14 UTCEPSS rescore
  2. 2026-06-07 15:21 UTCEPSS rescore
  3. 2026-06-06 13:44 UTCEPSS rescore
  4. 2026-06-06 13:44 UTCEPSS rescore
  5. 2026-06-05 22:43 UTCEPSS rescore
  6. 2026-06-05 22:43 UTCEPSS rescore
  7. 2026-06-05 06:07 UTCEPSS rescore
  8. 2026-06-05 06:07 UTCEPSS rescore
  9. 2026-06-04 13:09 UTCEPSS rescore
  10. 2026-06-04 13:09 UTCEPSS rescore
  11. 2026-06-02 20:10 UTCEPSS rescore
  12. 2026-06-02 20:10 UTCEPSS rescore
  13. 2026-05-31 22:28 UTCEPSS rescore
  14. 2026-05-31 12:59 UTCEG score recompute
  15. 2026-05-31 12:59 UTCGHSA enrichment
  16. 2026-05-31 00:13 UTCEPSS rescore
  17. 2026-05-31 00:13 UTCEPSS rescore
  18. 2026-05-28 13:42 UTCEPSS rescore
  19. 2026-05-28 13:42 UTCEPSS rescore
  20. 2026-05-28 13:42 UTCEPSS rescore
  21. 2026-05-27 13:37 UTCEPSS rescore
  22. 2026-05-26 07:16 UTCEPSS rescore
  23. 2026-05-26 07:16 UTCEPSS rescore
  24. 2026-05-24 16:42 UTCEPSS rescore
  25. 2026-05-22 21:15 UTCEPSS rescore
  26. 2026-05-21 22:38 UTCEPSS rescore
  27. 2026-05-20 22:36 UTCEPSS rescore
  28. 2026-05-20 22:36 UTCEPSS rescore
  29. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module) (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-18365✓ verified
    First seen Jan 14, 2012

    Microsoft Internet Explorer - JavaScript OnLoad Handler Remote Code Execution (MS05-054) (Metasploit)

    Open source ↗
  • Metasploitexploit/windows/browser/ms05_054_onload✓ verified
    First seen Nov 21, 2005

    MS05-054 Microsoft Internet Explorer JavaScript OnLoad Handler Remote Code Execution

    Open source ↗

Frequently asked(4)

What is CVE-2005-1790?
CVE-2005-1790 is a low vulnerability published on June 1, 2005. Microsoft Internet Explorer 6 SP2 6.0.2900.2180 and 6.0.2800.1106, and earlier versions, allows remote attackers to cause a denial of service (crash) and execute arbitrary code via a Javascript BODY onload event that calls the window function, aka "Mismatched Document Object Model Objects Memory…
When was CVE-2005-1790 disclosed?
CVE-2005-1790 was first published in the National Vulnerability Database on June 1, 2005, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2005-1790 actively exploited?
CVE-2005-1790 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 83% probability of exploitation in the next 30 days, which ranks it in the top 0.3% of all scored CVEs.
How do I remediate CVE-2005-1790?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-1790, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2005-1790

Explore →

Is Your Infrastructure Affected by CVE-2005-1790?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs