CVE-2007-3896

HIGHCVSS v2 · 9.39.3—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 9.3 — v2 rates that HIGH (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:M/Au:N/C:C/I:C/A:C. 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 53.8% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: epss, nvd_v2
Weaponized
9.3EG
EchelonGraph verdictMitigate this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 54%
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, epss high)
CISA-KEV: Not listedEPSS PROB: 54%CVSS v2: 9.3Exploit: Exploit-DB (verified) · epss top5pct · epss highExposed services: Not assessed

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

The URL handling in Shell32.dll in the Windows shell in Microsoft Windows XP and Server 2003, with Internet Explorer 7 installed, allows remote attackers to execute arbitrary programs via invalid "%" sequences in a mailto: or other URI handler, as demonstrated using mIRC, Outlook, Firefox, Adobe Reader, Skype, and other applications. NOTE: this issue might be related to other issues involving URL handlers in Windows systems, such as CVE-2007-3845. There also might be separate but closely related issues in the applications that are invoked by the handlers.

CVSS v2.0 (legacy)
9.3HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
9.3HIGHlow confidence
EG Risk
72
EG Risk 72/100CISA SSVC

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
Severity93% × 45%
Exploitation65% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.
EPSS PROB
54%
EPSS %ILE
98th
KEV
Not listed

CISA SSVCTrack at low, Track or Track* at medium and Track* or Attend at high mission impact.

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines at low or medium mission impact and sooner than that at high, and watch the vendor's advisory for the fix.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

October 11, 2007

Last Modified

April 23, 2026

References (40)

15 of 40 shown · show the other 25

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 13× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 25 repeat rows among the latest 98 are merged into the row they repeat.

  1. 2026-10-10 19:53 UTCEPSS rescoreEPSS 54% · 98th percentile
  2. 2026-10-09 20:00 UTCEPSS rescoreEPSS 54% · 98th percentile
  3. 2026-10-07 23:37 UTCEPSS rescoreEPSS 54% · 98th percentile
  4. 2026-10-06 15:09 UTCEPSS rescoreEPSS 54% · 98th percentile
  5. 2026-10-04 23:15 UTCEPSS rescoreEPSS 54% · 98th percentile
  6. 2026-10-03 14:20 UTCEPSS rescoreEPSS 54% · 98th percentile
  7. 2026-10-01 19:42 UTCEPSS rescoreEPSS 54% · 98th percentile
  8. 2026-09-30 14:57 UTCEPSS rescoreEPSS 54% · 98th percentile
  9. 2026-09-29 07:42 UTCEG score recompute
  10. 2026-09-18 19:20 UTCEPSS rescoreEPSS 54% · 98th percentile
  11. 2026-09-17 19:20 UTCEPSS rescoreEPSS 54% · 98th percentile
  12. 2026-09-15 03:04 UTCEPSS rescoreEPSS 54% · 98th percentile
  13. 2026-09-12 14:54 UTCEPSS rescoreEPSS 54% · 98th percentile
  14. 2026-09-05 15:22 UTCEPSS rescoreEPSS 54% · 98th percentile
  15. 2026-09-04 13:55 UTCEPSS rescoreEPSS 54% · 98th percentile
  16. 2026-08-30 01:14 UTCEPSS rescoreEPSS 54% · 98th percentile
  17. 2026-08-08 16:30 UTCEPSS rescoreEPSS 54% · 98th percentile
  18. 2026-08-06 13:41 UTCEPSS rescoreEPSS 54% · 98th percentile
  19. 2026-08-04 15:03 UTCEPSS rescoreEPSS 54% · 98th percentile
  20. 2026-08-03 10:28 UTCEPSS rescoreEPSS 54% · 98th percentile
  21. 2026-07-30 16:22 UTCEPSS rescoreEPSS 54% · 98th percentile
  22. 2026-07-30 01:25 UTCEPSS rescoreEPSS 54% · 98th percentile
  23. 2026-07-28 15:30 UTCEPSS rescoreEPSS 54% · 98th percentile
  24. 2026-07-26 13:33 UTCEG score recompute▲ 9.30
  25. 2026-07-25 14:12 UTCEPSS rescoreEPSS 54% · 98th percentile
Show 48 more
  1. 2026-07-24 14:11 UTCEPSS rescoreEPSS 54% · 98th percentile
  2. 2026-07-23 14:13 UTCEPSS rescoreEPSS 54% · 98th percentile
  3. 2026-07-23 00:54 UTCEG score recompute
  4. 2026-07-23 00:33 UTCEG score recompute▼ 3.90
  5. 2026-07-22 23:58 UTCEG score recompute▲ 3.90
  6. 2026-07-22 21:37 UTCEG score recompute
  7. 2026-07-22 14:03 UTCEPSS rescoreEPSS 54% · 98th percentile
  8. 2026-07-21 15:19 UTCEPSS rescoreEPSS 54% · 98th percentile
  9. 2026-07-20 17:03 UTCEPSS rescoreEPSS 54% · 98th percentile
  10. 2026-07-16 16:58 UTCEPSS rescoreEPSS 54% · 98th percentile
  11. 2026-07-15 16:54 UTCEPSS rescoreEPSS 54% · 98th percentile
  12. 2026-07-15 01:55 UTCEPSS rescoreEPSS 54% · 98th percentile
  13. 2026-07-13 06:07 UTCEPSS rescoreEPSS 54% · 98th percentile
  14. 2026-07-11 08:22 UTCEPSS rescoreEPSS 54% · 98th percentile
  15. 2026-07-05 02:26 UTCEPSS rescoreEPSS 54% · 98th percentile
  16. 2026-07-04 06:27 UTCEPSS rescoreEPSS 54% · 98th percentile
  17. 2026-07-02 14:00 UTCEPSS rescoreEPSS 54% · 98th percentile
  18. 2026-07-01 15:02 UTCEPSS rescoreEPSS 54% · 98th percentile
  19. 2026-06-30 23:19 UTCEPSS rescoreEPSS 54% · 98th percentile
  20. 2026-06-28 14:03 UTCEPSS rescoreEPSS 54% · 98th percentile
  21. 2026-06-28 04:52 UTCEPSS rescoreEPSS 54% · 98th percentile
  22. 2026-06-27 03:04 UTCEPSS rescoreEPSS 54% · 98th percentile
  23. 2026-06-25 13:46 UTCEPSS rescoreEPSS 54% · 98th percentile
  24. 2026-06-24 14:02 UTCEPSS rescoreEPSS 54% · 98th percentile
  25. 2026-06-23 21:29 UTCEPSS rescoreEPSS 54% · 98th percentile
  26. 2026-06-21 01:56 UTCEPSS rescoreEPSS 54% · 98th percentile
  27. 2026-06-19 19:22 UTCEPSS rescoreEPSS 54% · 98th percentile
  28. 2026-06-18 17:49 UTCEPSS rescoreEPSS 54% · 98th percentile
  29. 2026-06-17 17:49 UTCEPSS rescoreEPSS 54% · 98th percentile
  30. 2026-06-16 17:49 UTCEPSS rescoreEPSS 54% · 98th percentile
  31. 2026-06-15 17:44 UTCEPSS rescoreEPSS 54% · 98th percentile
  32. 2026-06-12 23:08 UTCEPSS rescoreEPSS 84% · 99th percentile
  33. 2026-06-10 22:14 UTCEPSS rescoreEPSS 84% · 99th percentile
  34. 2026-06-10 13:17 UTCEPSS rescoreEPSS 84% · 99th percentile
  35. 2026-06-07 15:21 UTCEPSS rescoreEPSS 84% · 99th percentile
  36. 2026-06-06 13:44 UTCEPSS rescoreEPSS 84% · 99th percentile
  37. 2026-06-05 22:44 UTCEPSS rescoreEPSS 84% · 99th percentile
  38. 2026-06-04 13:09 UTCEPSS rescoreEPSS 84% · 99th percentile
  39. 2026-06-02 20:10 UTCEPSS rescoreEPSS 84% · 99th percentile
  40. 2026-05-31 00:36 UTCEG score recompute
  41. 2026-05-31 00:36 UTCGHSA enrichmentGHSA-wmhg-7fm8-r4vp · GitHub severity HIGH
  42. 2026-05-31 00:13 UTCEPSS rescoreEPSS 84% · 99th percentile
  43. 2026-05-29 13:40 UTCEPSS rescoreEPSS 83% · 99th percentile
  44. 2026-05-28 13:42 UTCEPSS rescoreEPSS 83% · 99th percentile
  45. 2026-05-27 13:37 UTCEPSS rescoreEPSS 83% · 99th percentile
  46. 2026-05-21 22:38 UTCEPSS rescoreEPSS 83% · 99th percentile
  47. 2026-05-20 22:36 UTCEPSS rescoreEPSS 83% · 99th percentile
  48. 2026-05-18 21:29 UTCEPSS rescoreEPSS 83% · 99th percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-30645✓ verified
    Published Oct 5, 2007

    Microsoft Windows - URI Handler Command Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2007-3896?
CVE-2007-3896 is a high vulnerability published on October 11, 2007. The URL handling in Shell32.dll in the Windows shell in Microsoft Windows XP and Server 2003, with Internet Explorer 7 installed, allows remote attackers to execute arbitrary programs via invalid "%" sequences in a mailto: or other URI handler, as demonstrated using mIRC, Outlook, Firefox, Adobe…
When was the CVE record for CVE-2007-3896 published?
The CVE record for CVE-2007-3896 was published on October 11, 2007. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 23, 2026; the record at its source may have been updated since.
Is CVE-2007-3896 actively exploited?
CVE-2007-3896 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 54% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
How do I remediate CVE-2007-3896?
No fix for CVE-2007-3896 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2007-3896

Explore →

Is Your Infrastructure Affected by CVE-2007-3896?

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

Book a Demo →Browse All CVEs