CVE-2004-1037

HIGHCVSS v2 · 10.010.0
EchelonGraph scoreLOW confidence

“—” beside the score: it is equal to NVD's CVSS v2 base score.

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 10.0 — NVD rates that HIGH (NVD's v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; no CRITICAL band). Vector AV:N/AC:L/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 62% exploitation probability in the next 30 days; it does not lift the v2 base. EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized) sets EG Risk's exploitation input, not EPSS. Confidence: LOW.

Triggered by: NVD CVSS v2.0 (legacy fallback)
Sources: NVD CVSS v2.0
Weaponized

Also known asEUVD-2004-1035 (ENISA EUVD) · GHSA-7pfv-v495-qm3c (GitHub Security Advisories)Source: ENISA EUVD

10.0EG
EchelonGraph verdictPlan mitigationNo release containing the referenced fix is confirmed: check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 62%
  • Public exploit code is available (Metasploit, Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 62%CVSS v2: 10.0Exploit: Metasploit · Exploit-DB (verified)Exposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

The search function in TWiki 20030201 allows remote attackers to execute arbitrary commands via shell metacharacters in a search string.

CVSS v2.0 (legacy)
10.0HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
10.0HIGHlow confidence
EG Risk
71
EG Risk 71/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
Automatability0% × 15%
CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.
EPSS PROB
62%
EPSS %ILE
99th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v2.0 · CVSS v2.0AV:N/AC:L/Au:N/C:C/I:C/A:C
EG Likelihood
62% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it; until one is applied, restrict network exposure of the affected system or apply the vendor's mitigation on your normal schedule at low or medium mission impact and sooner than that at high.

Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from Vulnrichment. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

No released fix is confirmed on this page, but CISA's timeline does not wait for a fix's release: it starts when an agency identifies the flaw on an asset and updates the CDM Agency and Federal Dashboard, and the directive counts patching, decommissioning the system or another action as remediation. Until a fixed release is applied, mitigate as this page's verdict says. In the directive's words, “Fix on system upgrade” means that, “unless conditions change”, the vulnerability “should be remediated the next time the vulnerable asset receives a scheduled major upgrade or rebuild”: its timelines are “dynamic as facts change”, and a KEV listing shortens them.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 1, 2005

Last Modified

June 16, 2026

Data Freshness Timeline

(refreshed 10× in last 7d / 52× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 177 rows on record for this CVE.

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. None are among the latest 100 rows. The 77 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 14:13 UTCEchelonGraph re-scored
  2. 2026-11-22 14:13 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  3. 2026-11-21 15:59 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  4. 2026-11-20 17:46 UTCEchelonGraph re-scored
  5. 2026-11-20 17:46 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  6. 2026-11-20 16:25 UTCEPSS rescoreEPSS 62% · 99th percentile
  7. 2026-11-19 19:32 UTCEchelonGraph re-scored
  8. 2026-11-19 19:32 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  9. 2026-11-18 21:14 UTCEchelonGraph re-scored
  10. 2026-11-18 21:14 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  11. 2026-11-18 16:25 UTCEPSS rescoreEPSS 62% · 99th percentile
  12. 2026-11-17 23:01 UTCEchelonGraph re-scored
  13. 2026-11-17 23:01 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  14. 2026-11-17 00:48 UTCEchelonGraph re-scored
  15. 2026-11-17 00:48 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  16. 2026-11-16 02:34 UTCEchelonGraph re-scored
  17. 2026-11-16 02:34 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  18. 2026-11-15 02:50 UTCEchelonGraph re-scored
  19. 2026-11-15 02:50 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  20. 2026-11-14 16:25 UTCEPSS rescoreEPSS 62% · 99th percentile
  21. 2026-11-14 04:37 UTCEchelonGraph re-scored
  22. 2026-11-14 04:37 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  23. 2026-11-13 16:25 UTCEPSS rescoreEPSS 62% · 99th percentile
  24. 2026-11-13 06:06 UTCEchelonGraph re-scored
  25. 2026-11-13 06:06 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
Show 75 more
  1. 2026-11-12 16:24 UTCEPSS rescoreEPSS 62% · 99th percentile
  2. 2026-11-12 07:51 UTCEchelonGraph re-scored
  3. 2026-11-12 07:51 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  4. 2026-11-11 16:24 UTCEPSS rescoreEPSS 62% · 99th percentile
  5. 2026-11-11 09:38 UTCEchelonGraph re-scored
  6. 2026-11-11 09:38 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  7. 2026-11-10 16:25 UTCEPSS rescoreEPSS 62% · 99th percentile
  8. 2026-11-10 11:25 UTCEchelonGraph re-scored
  9. 2026-11-10 11:25 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  10. 2026-11-09 16:24 UTCEPSS rescoreEPSS 62% · 99th percentile
  11. 2026-11-09 13:12 UTCEchelonGraph re-scored
  12. 2026-11-09 13:12 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  13. 2026-11-08 16:25 UTCEPSS rescoreEPSS 62% · 99th percentile
  14. 2026-11-08 14:55 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  15. 2026-11-07 16:42 UTCEchelonGraph re-scored
  16. 2026-11-07 16:42 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  17. 2026-11-06 18:29 UTCEchelonGraph re-scored
  18. 2026-11-06 18:29 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  19. 2026-11-06 16:25 UTCEPSS rescoreEPSS 62% · 99th percentile
  20. 2026-11-05 20:15 UTCEchelonGraph re-scored
  21. 2026-11-05 20:15 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  22. 2026-11-04 22:02 UTCEchelonGraph re-scored
  23. 2026-11-04 22:02 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  24. 2026-11-04 16:25 UTCEPSS rescoreEPSS 62% · 99th percentile
  25. 2026-11-03 23:49 UTCEchelonGraph re-scored
  26. 2026-11-03 23:49 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  27. 2026-11-03 16:25 UTCEPSS rescoreEPSS 62% · 99th percentile
  28. 2026-11-03 01:36 UTCEchelonGraph re-scored
  29. 2026-11-03 01:36 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  30. 2026-11-02 03:23 UTCEchelonGraph re-scored
  31. 2026-11-02 03:23 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  32. 2026-11-01 05:11 UTCEchelonGraph re-scored
  33. 2026-11-01 05:11 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  34. 2026-10-31 16:24 UTCEPSS rescoreEPSS 62% · 99th percentile
  35. 2026-10-31 06:58 UTCEchelonGraph re-scored
  36. 2026-10-31 06:58 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  37. 2026-10-30 16:24 UTCEPSS rescoreEPSS 62% · 99th percentile
  38. 2026-10-30 08:45 UTCEchelonGraph re-scored
  39. 2026-10-30 08:45 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  40. 2026-10-29 16:25 UTCEPSS rescoreEPSS 62% · 99th percentile
  41. 2026-10-29 10:33 UTCEchelonGraph re-scored
  42. 2026-10-29 10:32 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  43. 2026-10-28 16:25 UTCEPSS rescoreEPSS 62% · 99th percentile
  44. 2026-10-28 12:18 UTCEchelonGraph re-scored
  45. 2026-10-28 12:18 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  46. 2026-10-27 16:24 UTCEPSS rescoreEPSS 62% · 99th percentile
  47. 2026-10-27 14:05 UTCEchelonGraph re-scored
  48. 2026-10-27 14:05 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  49. 2026-10-26 15:17 UTCEchelonGraph re-scored
  50. 2026-10-26 15:17 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  51. 2026-10-25 16:24 UTCEPSS rescoreEPSS 62% · 99th percentile
  52. 2026-10-25 16:06 UTCEchelonGraph re-scored
  53. 2026-10-25 16:06 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  54. 2026-10-24 17:51 UTCEchelonGraph re-scored
  55. 2026-10-24 17:51 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  56. 2026-10-24 16:25 UTCEPSS rescoreEPSS 62% · 99th percentile
  57. 2026-10-23 19:39 UTCEchelonGraph re-scored
  58. 2026-10-23 19:39 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  59. 2026-10-22 21:11 UTCEchelonGraph re-scored
  60. 2026-10-22 21:11 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  61. 2026-10-22 16:24 UTCEPSS rescoreEPSS 62% · 99th percentile
  62. 2026-10-21 22:59 UTCEchelonGraph re-scored
  63. 2026-10-21 22:58 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  64. 2026-10-21 16:24 UTCEPSS rescoreEPSS 62% · 99th percentile
  65. 2026-10-21 00:42 UTCEchelonGraph re-scored
  66. 2026-10-21 00:42 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  67. 2026-10-20 16:24 UTCEPSS rescoreEPSS 62% · 99th percentile
  68. 2026-10-20 02:28 UTCEchelonGraph re-scored
  69. 2026-10-20 02:27 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  70. 2026-10-19 16:25 UTCEPSS rescoreEPSS 62% · 99th percentile
  71. 2026-10-19 01:52 UTCEchelonGraph re-scored
  72. 2026-10-19 01:51 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH
  73. 2026-10-18 16:25 UTCEPSS rescoreEPSS 62% · 99th percentile
  74. 2026-10-18 03:39 UTCEchelonGraph re-scored
  75. 2026-10-18 03:39 UTCGHSA enrichmentGHSA-7pfv-v495-qm3c · GitHub severity HIGH

Publicly available exploits

(3 references)

Public exploit code is referenced for this CVE (1 Metasploit module, 2 Exploit-DB entries). No release with the fix is confirmed, so defenders should restrict or isolate affected systems accordingly until one is applied.

  • Exploit-DBEDB-16894✓ verified
    Published Jul 3, 2010

    TWiki - Search Function Arbitrary Command Execution (Metasploit)

    Open source ↗
  • Metasploitexploit/unix/webapp/twiki_search✓ verified
    Published Feb 21, 2010

    TWiki Search Function Arbitrary Command Execution

    Open source ↗
  • Exploit-DBEDB-642✓ verified
    Published Nov 20, 2004

    TWiki 20030201 - 'search.pm' Remote Command Execution

    Open source ↗

Frequently asked(4)

What is CVE-2004-1037?
CVE-2004-1037 is a high-severity vulnerability; its CVE record was published on March 1, 2005. The search function in TWiki 20030201 allows remote attackers to execute arbitrary commands via shell metacharacters in a search string.
When was CVE-2004-1037 made public?
CVE-2004-1037 was made public on November 12, 2004: that is the date its CVE record's CNA, MITRE Corporation, gives for when the vulnerability was made public. The CVE record itself was published on March 1, 2005. EchelonGraph's copy of the record carries a last-modified date of June 16, 2026; the record at its source may have been updated since.
Is CVE-2004-1037 actively exploited?
CVE-2004-1037 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it, and Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 62% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
How do I remediate CVE-2004-1037?
A fix for CVE-2004-1037 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2004-1037

Explore →

Is Your Infrastructure Affected by CVE-2004-1037?

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