# CVE-2017-8382: admidio CSRF Vulnerability

> Cross-site request forgery in admidio allows attackers to delete arbitrary user accounts by tricking authenticated users into clicking a malicious link.

- **Severity:** Medium 4.5 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 May 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-c4v8-2hg8-jv77

## What is CVE-2017-8382?

CVE-2017-8382 is a medium-severity vulnerability in n/a, published on 16 May 2017. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2017-8382?

2 open source packages ship an affected version, including admidio/admidio. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `admidio/admidio` | Packagist | All versions | 4.1-Beta.1 |
| `admidio/admidio` | Packagist | All versions | 4.1-Beta.1 |

Products: Admidio Admidio.

## How do I fix CVE-2017-8382?

Upgrade admidio/admidio to 4.1-Beta.1 or later.

## Is CVE-2017-8382 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-8382 exists.

Public exploit code:

- Admidio 3.2.8 Cross-Site Request Forgery Assigned CVE Number: CVE-2017-8382 (github_poc): https://github.com/faizzaidi/Admidio-3.2.8-CSRF-POC-by-Provensec-llc
- Admidio 3.2.8 - Cross-Site Request Forgery (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2024-37906](https://insights.sbomify.com/CVE-2024-37906/): Admidio has Blind SQL Injection in ecard_send.php (critical 10.0)
- [CVE-2021-32630](https://insights.sbomify.com/CVE-2021-32630/): Various (critical 9.6)
- [CVE-2026-32817](https://insights.sbomify.com/CVE-2026-32817/): Admidio is Missing Authorization and CSRF Protection on Document and Folder Deletion (critical 9.1)
- [CVE-2024-38529](https://insights.sbomify.com/CVE-2024-38529/): Admidio Vulnerable to RCE via Arbitrary File Upload in Message Attachment (critical 9.1)
- [CVE-2026-32756](https://insights.sbomify.com/CVE-2026-32756/): Admidio: Unrestricted File Upload via CSRF Token Validation Bypass in Documents & Files Module (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8382 and fix it if it is affected.

What it is: CVE-2017-8382 is a medium-severity vulnerability in n/a, published on 16 May 2017. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2017-8382 exists.

Affected packages and fixed versions:
- admidio/admidio (Packagist): affected all versions; fixed in 4.1-Beta.1
- admidio/admidio (Packagist): affected all versions; fixed in 4.1-Beta.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-8382/ (Markdown: https://insights.sbomify.com/CVE-2017-8382/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-8382
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-8382
- OSV: https://osv.dev/vulnerability/CVE-2017-8382

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-8382/
Summaries are generated and may contain mistakes; the official description above is the record.