How severe is CVE-2017-8382?

CVE-2017-8382 has a CVSS score of 4.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2017-8382?

CVE-2017-8382 affects the following packages: admidio/admidio (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2017-8382?

Update admidio/admidio to 4.1-Beta.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-8382 is resolved across your whole dependency graph.

How do I detect CVE-2017-8382 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for admidio/admidio, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2017-8382 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2017-8382 actively exploited in the wild?

Yes. There are 4 known exploit references for CVE-2017-8382, including 1 documented proof-of-concept exploit on Exploit-DB and 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2017-8382?

CVE-2017-8382 has an EPSS (Exploit Prediction Scoring System) score of 2.6%, placing it in the 86th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2017-8382?

CVE-2017-8382 is classified as Cross-Site Request Forgery (CSRF) (CWE-352). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2017-8382 published, and has it been updated?

CVE-2017-8382 was published on May 16, 2017 and was last updated on October 20, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2017-8382 — admidio

MEDIUMFix: Admidio/admidio#1074

CVE-2017-8382 is a medium-severity (CVSS 4.5) Cross-Site Request Forgery (CSRF) vulnerability in admidio/admidio. 4 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for admidio/admidio — see the affected versions and patch details below.

admidio CSRF Vulnerability

Also known asGHSA-c4v8-2hg8-jv77

Published

May 16, 2017

Updated

Oct 20, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

4 known

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

2.6%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs86th percentile — riskier than 86% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected

🐘admidio/admidio

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`admidio/admidio`	all versions	4.1-Beta.1`composer require admidio/admidio:^4.1-Beta.1`

Affected Products

1 product · 1 configurations

Application

admidioadmidio

1 version

3.2.8

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-42005webappsphp✓ Verified

Admidio 3.2.8 - Cross-Site Request Forgery

by Faiz Ahmed Zaidi · Apr 28, 2017

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for admidio/admidio, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update admidio/admidio to 4.1-Beta.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-8382 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

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

O3 Security · Impact-Aware SCA

Is CVE-2017-8382 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

None

Availability

High

Raw vector

CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:N/A:H

CWE Classification

CWE-352Cross-Site Request Forgery (CSRF)

Weaponization

No Nuclei template or Metasploit module yet. 4 public proof-of-concept references are listed on this page.

Timeline

First exploit

Apr 28, 2017

Disclosed

May 16, 2017

Last updated

Oct 20, 2026

Identifiers

CVE-2017-8382

GHSA-c4v8-2hg8-jv77

References

Advisorynvd.nist.gov · CVE 2017 8382 Reportgithub.com Weben.0day.today Webgithub.com Webgithub.com · a7ac9d3c9e0780e877fe9ac846ac64b284de8553 Webexploit-db.com Packagegithub.com · Admidio 3.2.8 CSRF POC by Provensec llc Packagegithub.com · admidio Evidenceexploit-db.com

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting admidio/admidio are rated as high or higher (top: high).

CVE-2026-53760CVE-2026-47232CVE-2026-47234CVE-2026-47228CVE-2026-47230CVE-2026-47226CVE-2026-47227CVE-2026-47231

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 20, 2026