CVE-2008-7220

HIGHCVSS v2 · 7.57.5—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.5 — 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:L/Au:N/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 13.4% 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
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 13%CVSS v2: 7.5Exploit: Elevated riskExposed: 0

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

Unspecified vulnerability in Prototype JavaScript framework (prototypejs) before 1.6.0.2 allows attackers to make "cross-site ajax requests" via unknown vectors.

CVSS v2.0 (legacy)
7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.5(low)
EG Risk
54(Track)
EG Risk 54/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
Severity75% × 45%
Exploitation40% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
13%
EPSS %ILE
96%
KEV
Not listed

Published

September 13, 2009

Last Modified

April 23, 2026

References (40)

Affected Packages

(31 across 5 ecosystems)
Debian:11(9)
PackageVulnerable rangeFixed inDependents
asterisk—1:1.6.2.0~rc3-1—
jscropperui—1.2.1-1—
libaws—2.7-1—
libhtml-prototype-perl—1.48-3—
otrs22.0.4p01-10 ... 2.3.4-5 (49 versions)2.3.4-6—
prototypejs—1.6.0.2-1—
scriptaculous—1.8.3-1—
symfony—1.0.21-1.1—
wordpress—2.5.0-2—
Debian:14(8)
PackageVulnerable rangeFixed inDependents
asterisk0.1.11-3 ... 1:1.6.2.0~dfsg~rc1-1 (110 versions)1:1.6.2.0~rc3-1—
exaile—0.2.14+debian-2.2—
jscropperui—1.2.1-1—
libhtml-prototype-perl—1.48-3—
prototypejs—1.6.0.2-1—
scriptaculous—1.8.3-1—
symfony—1.0.21-1.1—
wordpress—2.5.0-2—
Debian:13(7)
PackageVulnerable rangeFixed inDependents
exaile—0.2.14+debian-2.2—
jscropperui—1.2.1-1—
libhtml-prototype-perl—1.48-3—
prototypejs—1.6.0.2-1—
scriptaculous—1.8.3-1—
symfony—1.0.21-1.1—
wordpress—2.5.0-2—
Debian:12(6)
PackageVulnerable rangeFixed inDependents
jscropperui—1.2.1-1—
libhtml-prototype-perl—1.48-3—
prototypejs—1.6.0.2-1—
scriptaculous—1.8.3-1—
symfony—1.0.21-1.1—
wordpress—2.5.0-2—
Debian:5.0(1)
PackageVulnerable rangeFixed inDependents
asterisk1:1.4.21.2~dfsg-31:1.4.21.2~dfsg-3+lenny1—

Data Freshness Timeline

(refreshed 3× in last 7d / 10× 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 109 total refreshes for this CVE.

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

Frequently asked(4)

What is CVE-2008-7220?
CVE-2008-7220 is a high vulnerability published on September 13, 2009. Unspecified vulnerability in Prototype JavaScript framework (prototypejs) before 1.6.0.2 allows attackers to make "cross-site ajax requests" via unknown vectors.
When was CVE-2008-7220 disclosed?
CVE-2008-7220 was first published in the National Vulnerability Database on September 13, 2009, 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-2008-7220 actively exploited?
CVE-2008-7220 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 13% probability of exploitation in the next 30 days, which ranks it in the top 3.9% of all scored CVEs.
How do I remediate CVE-2008-7220?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2008-7220, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2008-7220

Explore →

Is Your Infrastructure Affected by CVE-2008-7220?

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

Start Free Scan →Browse All CVEs