CVE-2017-8382

MEDIUMNVD 4.54.5
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.5 under NVD CVSS v3. EPSS exploit probability: 2.6% (85th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this weekWeaponized
4.5EG
EchelonGraph verdictPlan a fixRemediate 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, other public proof-of-concept code)
CISA-KEV: Not listedEPSS PROB: 2.6%CVSS: 4.5Exploit: Exploit-DB (verified) · other public PoCExposed services: Not assessed

A fix is available — apply it.

admidio 3.2.8 has CSRF in adm_program/modules/members/members_function.php with an impact of deleting arbitrary user accounts.

CVSS v3
4.5
EG Score
4.5MEDIUMmedium confidence
EG Risk
46
EG Risk 46/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)
Severity45% × 45%
The EG Score, 4.5 of 10.
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 available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
2.6%
EPSS %ILE
85th
KEV
Not listed

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

A fix is available. Apply it within your standard update timelines 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.

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

May 16, 2017

Last Modified

June 17, 2026

References (4)

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
admidio/admidio—
  • every version up to 4.1-Beta.1: fixed in 4.1-Beta.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 26× 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 84 of 175 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. 16 repeat rows among the latest 100 are merged into the row they repeat. The 91 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(2 references)

Public exploit code is referenced for this CVE (1 Exploit-DB entry, 1 GitHub PoC). Defenders should treat patch urgency accordingly.

  • Exploit-DBEDB-42005✓ verified
    Published Apr 28, 2017

    Admidio 3.2.8 - Cross-Site Request Forgery

    Open source ↗
  • GitHub PoCfaizzaidi/Admidio-3.2.8-CSRF-POC-by-Provensec-llc
    Published May 21, 2017

    Admidio 3.2.8 Cross-Site Request Forgery Assigned CVE Number: CVE-2017-8382

    Open source ↗

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2017-8382?
CVE-2017-8382 is a medium-severity vulnerability; its CVE record was published on May 16, 2017. admidio 3.2.8 has CSRF in admprogram/modules/members/membersfunction.php with an impact of deleting arbitrary user accounts.
When was CVE-2017-8382 made public?
CVE-2017-8382 was made public on May 16, 2017: 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 May 16, 2017. EchelonGraph's copy of the record carries a last-modified date of June 17, 2026; the record at its source may have been updated since.
Is CVE-2017-8382 actively exploited?
CVE-2017-8382 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.6% probability of exploitation in the next 30 days (85th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2017-8382?
CVE-2017-8382 has a CVSS v3 base score of 4.5 (NVD).
How do I remediate CVE-2017-8382?
A fix for CVE-2017-8382 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2017-8382

Explore →

Is Your Infrastructure Affected by CVE-2017-8382?

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

Book a Demo →Browse All CVEs