CVE-2003-1025

MEDIUMCVSS v2 · 4.34.3—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 4.3 — v2 rates that MEDIUM (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:N/I:P/A:N. 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 26.9% 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
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 27%CVSS v2: 4.3Exploit: Exploit-DB (verified) · epss top5pct · public exploitExposed: 0

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

Internet Explorer 5.01 through 6 SP1 allows remote attackers to spoof the domain of a URL via a "%01" character before an @ sign in the user@domain portion of the URL, which hides the rest of the URL, including the real site, in the address bar, aka the "Improper URL Canonicalization Vulnerability."

CVSS v2.0 (legacy)
4.3MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
4.3(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
Severity43% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
27%
EPSS %ILE
98%
KEV
Not listed

Published

January 20, 2004

Last Modified

June 16, 2026

References (26)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 21× 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-07-26 13:23 UTCEG score recompute▲ 4.30
  2. 2026-07-25 14:11 UTCEPSS rescore
  3. 2026-07-24 14:11 UTCEPSS rescore
  4. 2026-07-23 00:45 UTCEG score recompute
  5. 2026-07-23 00:26 UTCEG score recompute
  6. 2026-07-22 23:49 UTCEG score recompute
  7. 2026-07-22 21:30 UTCEG score recompute
  8. 2026-07-20 17:02 UTCEPSS rescore
  9. 2026-07-19 14:25 UTCEPSS rescore
  10. 2026-07-18 09:59 UTCEPSS rescore
  11. 2026-07-18 09:59 UTCEPSS rescore
  12. 2026-07-16 16:58 UTCEPSS rescore
  13. 2026-07-15 01:55 UTCEPSS rescore
  14. 2026-07-15 01:55 UTCEPSS rescore
  15. 2026-07-13 06:07 UTCEPSS rescore
  16. 2026-07-11 08:22 UTCEPSS rescore
  17. 2026-07-11 08:22 UTCEPSS rescore
  18. 2026-07-08 15:09 UTCEPSS rescore
  19. 2026-07-04 06:26 UTCEPSS rescore
  20. 2026-07-02 14:00 UTCEPSS rescore
  21. 2026-06-28 04:52 UTCEPSS rescore
  22. 2026-06-27 03:04 UTCEPSS rescore
  23. 2026-06-23 21:29 UTCEPSS rescore
  24. 2026-06-21 01:56 UTCEPSS rescore
  25. 2026-06-18 17:49 UTCEPSS rescore
Show 29 more
  1. 2026-06-18 17:49 UTCEPSS rescore
  2. 2026-06-17 17:49 UTCEPSS rescore
  3. 2026-06-17 17:49 UTCEPSS rescore
  4. 2026-06-16 17:49 UTCEPSS rescore
  5. 2026-06-16 17:49 UTCEPSS rescore
  6. 2026-06-15 17:43 UTCEPSS rescore
  7. 2026-06-13 22:56 UTCEPSS rescore
  8. 2026-06-12 23:08 UTCEPSS rescore
  9. 2026-06-11 13:55 UTCEPSS rescore
  10. 2026-06-10 22:13 UTCEPSS rescore
  11. 2026-06-10 13:17 UTCEPSS rescore
  12. 2026-06-05 22:43 UTCEPSS rescore
  13. 2026-06-05 22:43 UTCEPSS rescore
  14. 2026-06-05 06:07 UTCEPSS rescore
  15. 2026-06-02 20:10 UTCEPSS rescore
  16. 2026-06-01 13:49 UTCEPSS rescore
  17. 2026-06-01 13:49 UTCEPSS rescore
  18. 2026-05-31 16:39 UTCEG score recompute
  19. 2026-05-31 16:39 UTCGHSA enrichment
  20. 2026-05-29 13:40 UTCEPSS rescore
  21. 2026-05-29 13:40 UTCEPSS rescore
  22. 2026-05-27 13:37 UTCEPSS rescore
  23. 2026-05-26 07:16 UTCEPSS rescore
  24. 2026-05-26 07:16 UTCEPSS rescore
  25. 2026-05-24 16:42 UTCEPSS rescore
  26. 2026-05-22 21:15 UTCEPSS rescore
  27. 2026-05-20 22:36 UTCEPSS rescore
  28. 2026-05-18 21:29 UTCEPSS rescore
  29. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(3 references)

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

  • Exploit-DBEDB-23465✓ verified
    First seen Dec 23, 2003

    Opera Browser 6.0 6 - URI Display Obfuscation

    Open source ↗
  • Exploit-DBEDB-23422✓ verified
    First seen Dec 9, 2003

    Microsoft Internet Explorer 5/6 / Mozilla 1.2.1 - URI Display Obfuscation (1)

    Open source ↗
  • Exploit-DBEDB-23423✓ verified
    First seen Dec 9, 2003

    Microsoft Internet Explorer 5/6 / Mozilla 1.2.1 - URI Display Obfuscation (2)

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2003-1025?
CVE-2003-1025 is a medium vulnerability published on January 20, 2004. Internet Explorer 5.01 through 6 SP1 allows remote attackers to spoof the domain of a URL via a "%01" character before an @ sign in the user@domain portion of the URL, which hides the rest of the URL, including the real site, in the address bar, aka the "Improper URL Canonicalization Vulnerability."
When was CVE-2003-1025 disclosed?
CVE-2003-1025 was first published in the National Vulnerability Database on January 20, 2004, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2003-1025 actively exploited?
CVE-2003-1025 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 27% probability of exploitation in the next 30 days, which ranks it in the top 2.2% of all scored CVEs.
How do I remediate CVE-2003-1025?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2003-1025, 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-2003-1025

Explore →

Is Your Infrastructure Affected by CVE-2003-1025?

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

Start Free Scan →Browse All CVEs