CVE-2017-8382 json
admidio CSRF Vulnerability
published 2017-05-16 9 y ago modified 2026-06-17 4 mo ago also GHSA-c4v8-2hg8-jv77 , EUVD-2022-3509
- cvss
- 4.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 1
- Exploit-DB
Summary
admidio 3.2.8 has CSRF in adm_program/modules/members/members_function.php with an impact of deleting arbitrary user accounts.
Patch / fix
- packagist admidio/admidio 4.1-Beta.1
- github.com/Admidio/admidio@a7ac9d3 commit
- github.com/Admidio/admidio#1074 pull request
Timeline
- First public exploit (EDB-42005)
- Published
Exploit prediction
2.63% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-42005 Admidio 3.2.8 - Cross-Site Request Forgery webapps, 2017-04-28
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 4.5 | CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 3.5 | AV:N/AC:M/Au:S/C:N/I:N/A:P |
| GitHub | 3.0 | 4.5 | CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | admidio/admidio | <4.1-Beta.1 |
4.1-Beta.1 |
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/Admidio/admidio/pull/1074
web
-
github.com
/Admidio/admidio/commit/a7ac9d3c9e0780e877fe9ac846ac64b284de8553
web
-
exploit-db.com
/exploits/42005/
exploit, third-party-advisory
-
en.0day.today
/exploit/27771
web
-
github.com
/faizzaidi/Admidio-3.2.8-CSRF-POC-by-Provensec-llc
web
-
github.com
/Admidio/admidio/issues/612
web
-
nvd.nist.gov
/vuln/detail/CVE-2017-8382
advisory
-
github.com
/Admidio/admidio
package
-
exploit-db.com
/exploits/42005
web
Sources
- CVE List CVE-2017-8382
- GitHub Advisory GHSA-c4v8-2hg8-jv77
- NVD CVE-2017-8382
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.