CVE-2007-5685

MEDIUMCVSS v2 · 5.05.0—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 5.0 — 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:N/C:P/I:N/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 3.5% 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
5.0EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 3.5%CVSS v2: 5.0Exploit: Exploit-DB (verified) · public exploitExposed 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 safe_path function in shttp before 0.0.5 allows remote attackers to conduct directory traversal attacks and read files via a combination of ".." and sub-directory specifiers that resolve to a pathname that is at or below the same level as the web document root, but in a different part of the directory tree.

CVSS v2.0 (legacy)
5.0MEDIUMNVD never assigned a CVSS v3 rating to this CVE
EG Score
5.0MEDIUMlow confidence
EG Risk
53
EG Risk 53/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
Severity50% × 45%
Exploitation65% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
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 and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
3.5%
EPSS %ILE
88th
KEV
Not listed

CISA SSVCTrack at low, Track or Track* at medium and Track* or 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 and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

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 28, 2007

Last Modified

April 23, 2026

References (12)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 13× 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.

Showing the most recent 100 of 124 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

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

  • Exploit-DBEDB-30711✓ verified
    First seen Oct 25, 2007

    Shttp 0.0.x - Directory Traversal

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2007-5685?
CVE-2007-5685 is a medium vulnerability published on October 28, 2007. The safe_path function in shttp before 0.0.5 allows remote attackers to conduct directory traversal attacks and read files via a combination of ".." and sub-directory specifiers that resolve to a pathname that is at or below the same level as the web document root, but in a different part of the…
When was CVE-2007-5685 disclosed?
CVE-2007-5685 was first published on October 28, 2007, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2007-5685 actively exploited?
CVE-2007-5685 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 3.5% probability of exploitation in the next 30 days (88th percentile of EPSS-scored CVEs).
How do I remediate CVE-2007-5685?
A fix for CVE-2007-5685 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-2007-5685

Explore →

Is Your Infrastructure Affected by CVE-2007-5685?

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

Book a Demo →Browse All CVEs