CVE-2026-32816

MEDIUMPre-NVD 5.75.7
EchelonGraph scoreMEDIUM confidence

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

Score 5.7 from GitHub Security Advisory (severity: MODERATE) published 2026-03-16. A secondary CVSS source baseline 5.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-13394 (ENISA EUVD) · GHSA-wwg8-6ffr-h4q2 (GitHub Security Advisories)Source: ENISA EUVD

5.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Admidio is an open-source user management solution. In versions 5.0.0 through 5.0.6, the delete, activate, and deactivate modes in modules/groups-roles/groups_roles.php perform destructive state changes on organizational roles but never validate an anti-CSRF token. The client-side UI passes a CSRF token to callUrlHideElement(), which includes it in the POST body, but the server-side handlers ignore $_POST["adm_csrf_token"] entirely for these three modes. An attacker who can discover a role UUID (visible in the public cards view when the module is publicly accessible) can embed a forged POST form on any external page and trick any user with the rol_assign_roles right into deleting or toggling roles for the organization. Role deletion is permanent and cascades to all memberships, event associations, and rights data. If exploited, an attacker can trick any user with delegated role-assignment rights into permanently deleting roles, mass-revoking all associated memberships and access to events, documents, and mailing lists, or silently activating or deactivating entire groups, with target role UUIDs trivially harvested from the unauthenticated public cards view and no undo path short of a database restore. This issue has been fixed in version 5.0.7.

CVSS v3
5.7
EG Score
5.7MEDIUMmedium confidence
EG Risk
42
EG Risk 42/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity57% × 45%
Impact severity (EG Severity): CVSS 5.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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.
EPSS PROB
0.1%
EPSS %ILE
2nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.7): severity, escalated by confirmed exploitation. This CVE's 5.7 is its impact severity (EG Severity), not escalated.

EG Severity
5.7 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (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)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). 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

March 19, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Aug 6, 2026
Patch available. Sources: github_release, github.
GitHub advisoryMentions a patch (unverified)

Missing CSRF Validation on Role Delete, Activate, and Deactivate Actions · Advisory · Admidio/admidio · GitHub

https://github.com/Admidio/admidio/security/advisories/GHSA-wwg8-6ffr-h4q2
GitHub release Patch Available

5.0.7

Patch available: Admidio/admidio v5.0.7

https://github.com/Admidio/admidio/releases/tag/v5.0.7

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
composeradmidio/admidio @ 5.0.7 (fixes >= 5.0.0, <= 5.0.6)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFix by version rangeDependents
admidio/admidiov5.0.0 ... v5.0.6 (7 versions)
  • 5.0.0 up to 5.0.7: fixed in 5.0.7
—

Weakness Classification(1)

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

Data Freshness Timeline

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

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-11-01 07:54 UTCGHSA enrichmentGHSA-wwg8-6ffr-h4q2 · GitHub severity MODERATE · GitHub CVSS 5.7
  3. 2026-11-01 07:54 UTCEG score recompute
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-27 09:25 UTCOSV refresh
  9. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-25 14:35 UTCEG score recompute
  12. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  14. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  15. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  16. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  17. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  18. 2026-10-18 03:47 UTCEG score recompute
  19. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  20. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.2% · 7th percentile
  21. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  22. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  23. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  24. 2026-10-12 16:04 UTCEG score recompute
  25. 2026-10-11 19:56 UTCEG score recompute
Show 71 more
  1. 2026-10-11 17:09 UTCEG score recompute
  2. 2026-10-11 14:36 UTCEG score recompute
  3. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  4. 2026-10-11 07:55 UTCOSV refresh
  5. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  6. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  7. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  8. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  9. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  10. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  11. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  12. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  13. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  14. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  15. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  16. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  17. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  18. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  19. 2026-09-21 21:01 UTCOSV refresh
  20. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  21. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  22. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  23. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  24. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  25. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  26. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  27. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  28. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  29. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  30. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  31. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  32. 2026-09-02 17:08 UTCOSV refresh
  33. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  34. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  35. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  36. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  37. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  38. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  39. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  40. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  41. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  42. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  43. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  44. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  45. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  46. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  47. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  48. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  49. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  50. 2026-08-16 11:07 UTCEG score recompute
  51. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  52. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  53. 2026-08-14 07:17 UTCEG score recompute
  54. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  55. 2026-08-12 22:00 UTCEG score recompute
  56. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  57. 2026-08-11 06:09 UTCEG score recompute
  58. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  59. 2026-08-10 06:30 UTCEG score recompute
  60. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  61. 2026-08-09 06:50 UTCEG score recompute
  62. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  63. 2026-08-07 17:20 UTCEG score recompute
  64. 2026-08-06 13:46 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  65. 2026-08-06 01:31 UTCEG score recompute
  66. 2026-08-05 19:17 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  67. 2026-08-04 15:10 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  68. 2026-08-04 10:38 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  69. 2026-08-04 00:39 UTCEG score recompute
  70. 2026-08-03 10:36 UTCEPSS rescoreEPSS 0.1% · 3rd percentile
  71. 2026-08-02 16:24 UTCEG score recompute

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-32816?
CVE-2026-32816 is a medium-severity vulnerability; its CVE record was published on March 19, 2026. Admidio is an open-source user management solution. In versions 5.0.0 through 5.0.6, the delete, activate, and deactivate modes in modules/groups-roles/groups_roles.php perform destructive state changes on organizational roles but never validate an anti-CSRF token. The client-side UI passes a CSRF…
When was the CVE record for CVE-2026-32816 published?
The CVE record for CVE-2026-32816 was published on March 19, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. 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-2026-32816 actively exploited?
CVE-2026-32816 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-32816?
CVE-2026-32816 has a CVSS base score of 5.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-32816?
A fix for CVE-2026-32816 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-2026-32816

Explore →

Is Your Infrastructure Affected by CVE-2026-32816?

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

Book a Demo →Browse All CVEs