CVE-2006-5000

MEDIUMCVSS v2 · 6.56.5—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 6.5 — 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:L/Au:S/C:P/I:P/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 63.8% 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
Elevated
6.5EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 65%
CISA-KEV: Not listedEPSS PROB: 65%CVSS v2: 6.5Exploit: Elevated riskExposed: 0

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

Multiple buffer overflows in WS_FTP Server 5.05 before Hotfix 1, and possibly other versions down to 5.0, have unknown impact and remote authenticated attack vectors via the (1) XCRC, (2) XMD5, and (3) XSHA1 commands. NOTE: in the early publication of this identifier on 20060926, the description was used for the wrong issue.

CVSS v2.0 (legacy)
6.5MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
6.5(low)
EG Risk
59(Track)
EG Risk 59/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
Severity65% × 45%
Exploitation64% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
65%
EPSS %ILE
99%
KEV
Not listed

Published

September 26, 2006

Last Modified

April 16, 2026

References (10)

Data Freshness Timeline

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

Frequently asked(4)

What is CVE-2006-5000?
CVE-2006-5000 is a medium vulnerability published on September 26, 2006. Multiple buffer overflows in WS_FTP Server 5.05 before Hotfix 1, and possibly other versions down to 5.0, have unknown impact and remote authenticated attack vectors via the (1) XCRC, (2) XMD5, and (3) XSHA1 commands. NOTE: in the early publication of this identifier on 20060926, the description…
When was CVE-2006-5000 disclosed?
CVE-2006-5000 was first published in the National Vulnerability Database on September 26, 2006, 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-2006-5000 actively exploited?
CVE-2006-5000 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 65% probability of exploitation in the next 30 days, which ranks it in the top 0.8% of all scored CVEs.
How do I remediate CVE-2006-5000?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2006-5000, 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-2006-5000

Explore →

Is Your Infrastructure Affected by CVE-2006-5000?

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

Start Free Scan →Browse All CVEs