CVE-2008-1971

HIGHCVSS v2 · 7.57.5
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 7.5 — 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: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 2.2% 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
7.5EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • Public exploit code is available (Exploit-DB, marked verified by Exploit-DB)
CISA-KEV: Not listedEPSS PROB: 2.2%CVSS v2: 7.5Exploit: Exploit-DB (verified)Exposed services: Not assessed

No fix has been recorded since the CVE record was published in 2008 — if the vendor still supports the product, apply the fixed version it names; if not, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

phShoutBox Final 1.5 and earlier only checks passwords when specified in $_POST, which allows remote attackers to gain privileges by setting the (1) phadmin cookie to admin.php, or (2) in 1.4 and earlier, the ssbadmin cookie to shoutadmin.php.

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

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 (value × EchelonGraph’s weight)
Severity75% × 45%
The EG Score, 7.5 of 10.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
Automatability30% × 15%
EchelonGraph's default before algorithm v3.4: CISA had not published Automatable for this CVE.
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track or Track* at medium and Track* or Attend at high mission impact.
Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). 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: No fix has been recorded since the CVE record was published in 2008. If the vendor still supports the product, apply the fixed version it names within your standard update timelines at low or medium mission impact and sooner than that at high; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.
EPSS PROB
2.2%
EPSS %ILE
82nd
KEV
Not listed

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

No fix has been recorded since the CVE record was published in 2008. If the vendor still supports the product, apply the fixed version it names within your standard update timelines at low or medium mission impact and sooner than that at high; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact unknown (not published for this CVE). 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

Published

April 27, 2008

Last Modified

April 23, 2026

References (4)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 17× 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 it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 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). Most recent first.

Showing the most recent 82 of 111 refreshes 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. 18 repeat rows among the latest 100 are merged into the row they repeat. The 29 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 13:38 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  2. 2026-10-10 19:53 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  3. 2026-10-09 20:00 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  4. 2026-10-08 16:33 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  5. 2026-10-07 23:37 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  6. 2026-10-06 15:09 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  7. 2026-10-05 17:37 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  8. 2026-10-03 14:20 UTCEPSS rescoreEPSS 2.2% · 82nd percentile
  9. 2026-10-01 19:42 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  10. 2026-09-30 14:57 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  11. 2026-09-29 07:49 UTCEG score recompute
  12. 2026-09-26 15:52 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  13. 2026-09-18 19:20 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  14. 2026-09-17 19:20 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  15. 2026-09-15 03:04 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  16. 2026-09-13 16:40 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  17. 2026-09-12 14:54 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  18. 2026-09-10 09:24 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  19. 2026-09-06 13:41 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  20. 2026-09-05 15:22 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  21. 2026-09-04 13:55 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  22. 2026-09-04 04:59 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  23. 2026-08-30 01:14 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  24. 2026-08-28 21:34 UTCEPSS rescoreEPSS 2.2% · 81st percentile
  25. 2026-08-15 01:24 UTCEPSS rescoreEPSS 2.2% · 81st percentile
Show 57 more
  1. 2026-08-08 16:31 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  2. 2026-08-07 16:21 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  3. 2026-08-06 13:41 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  4. 2026-08-05 19:11 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  5. 2026-08-04 15:03 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  6. 2026-08-03 10:28 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  7. 2026-07-30 01:25 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  8. 2026-07-26 13:35 UTCEG score recomputeFirst assessed: 7.5 HIGH
  9. 2026-07-25 14:12 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  10. 2026-07-24 14:12 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  11. 2026-07-23 14:14 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  12. 2026-07-23 00:56 UTCEG score recompute
  13. 2026-07-23 00:34 UTCEG score recompute
  14. 2026-07-23 00:00 UTCEG score recompute
  15. 2026-07-22 21:39 UTCEG score recompute
  16. 2026-07-20 17:03 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  17. 2026-07-18 09:59 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  18. 2026-07-16 16:58 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  19. 2026-07-15 16:54 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  20. 2026-07-15 01:55 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  21. 2026-07-13 22:25 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  22. 2026-07-13 06:07 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  23. 2026-07-11 08:22 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  24. 2026-07-09 19:04 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  25. 2026-07-08 15:09 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  26. 2026-07-06 16:23 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  27. 2026-07-06 02:19 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  28. 2026-07-05 02:26 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  29. 2026-07-04 06:27 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  30. 2026-07-02 14:00 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  31. 2026-07-01 15:02 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  32. 2026-06-30 23:19 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  33. 2026-06-29 14:02 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  34. 2026-06-28 14:03 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  35. 2026-06-28 04:52 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  36. 2026-06-27 03:04 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  37. 2026-06-25 13:46 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  38. 2026-06-24 14:02 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  39. 2026-06-23 21:29 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  40. 2026-06-21 14:53 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  41. 2026-06-19 19:22 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  42. 2026-06-18 17:49 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  43. 2026-06-17 17:49 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  44. 2026-06-16 17:49 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  45. 2026-06-15 17:44 UTCEPSS rescoreEPSS 2.2% · 80th percentile
  46. 2026-06-14 23:13 UTCEPSS rescoreEPSS 5.2% · 90th percentile
  47. 2026-06-13 22:57 UTCEPSS rescoreEPSS 5.2% · 90th percentile
  48. 2026-06-12 23:08 UTCEPSS rescoreEPSS 5.2% · 90th percentile
  49. 2026-06-11 13:56 UTCEPSS rescoreEPSS 5.2% · 90th percentile
  50. 2026-06-10 22:14 UTCEPSS rescoreEPSS 5.2% · 90th percentile
  51. 2026-06-10 13:17 UTCEPSS rescoreEPSS 5.2% · 90th percentile
  52. 2026-06-08 14:13 UTCEPSS rescoreEPSS 5.2% · 90th percentile
  53. 2026-06-07 15:22 UTCEPSS rescoreEPSS 5.2% · 90th percentile
  54. 2026-06-06 13:44 UTCEPSS rescoreEPSS 5.2% · 90th percentile
  55. 2026-06-05 22:44 UTCEPSS rescoreEPSS 5.2% · 90th percentile
  56. 2026-06-05 06:07 UTCEPSS rescoreEPSS 5.2% · 90th percentile
  57. 2026-06-04 13:09 UTCEPSS rescoreEPSS 5.2% · 90th percentile

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Exploit-DB entry). No fix is on record, so defenders should restrict or isolate affected systems accordingly.

  • Exploit-DBEDB-5467✓ verified
    Published Apr 18, 2008

    PhShoutBox 1.5 - Insecure Cookie Handling

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2008-1971?
CVE-2008-1971 is a high-severity vulnerability; its CVE record was published on April 27, 2008. phShoutBox Final 1.5 and earlier only checks passwords when specified in $_POST, which allows remote attackers to gain privileges by setting the (1) phadmin cookie to admin.php, or (2) in 1.4 and earlier, the ssbadmin cookie to shoutadmin.php.
When was CVE-2008-1971 made public?
CVE-2008-1971 was made public on April 18, 2008: 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 April 27, 2008. EchelonGraph's copy of the record carries a last-modified date of April 23, 2026; the record at its source may have been updated since.
Is CVE-2008-1971 actively exploited?
CVE-2008-1971 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: Exploit-DB marks a public exploit for it as verified. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 2.2% probability of exploitation in the next 30 days (82nd percentile of EPSS-scored CVEs).
How do I remediate CVE-2008-1971?
No fix for CVE-2008-1971 has been recorded since its CVE record was published in 2008. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2008-1971

Explore →

Is Your Infrastructure Affected by CVE-2008-1971?

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

Book a Demo →Browse All CVEs