Admidio has Missing CSRF Protections on Custom List Deletion in mylist_function.php
CVE-2026-34382GHSA-g3mx-8jm6-rc85
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (admidio/admidio 5.0.8), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist admidio/admidio
- Affected
- >= 5.0.0, <= 5.0.7
- Fixed in
- 5.0.8
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-g3mx-8jm6-rc85 lists affected ranges: Packagist admidio/admidio >=5.0.0 <=5.0.7
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 4.6 · CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L
- EPSS
- CVE-2026-34382: 0.13% estimated exploitation activity in the next 30 days; percentile 2.45 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Reported by: Juan Felipe Oz @JF0x0r LinkedIn Summary The delete mode handler in mylistfunction.php permanently deletes list configurations without validating a CSRF token. An attacker who can lure an authenticated user to a malicious page can silently destroy that user's list configurations — including organization-wide shared lists when the victim holds administrator rights. Vulnerable Code File: modules/groups-roles/mylistfunction.php The CSRF token validation at lines 81–82 is scoped exclusively to the save, saveas, and savetemporary modes: <img width="857" height="162" alt="imagen" src="https://github.com/user-attachments/assets/caec390e-ba6f-40f0-bb9c-a8870679da3d" / The delete case at lines 159–161 executes the destructive operation with no token check: <img width="560" height="133" alt="imagen" src="https://github.com/user-attachments/assets/2d5eff8e-bbce-49b9-b6d5-77f4e2e6db69" / A global input guard at lines 40–48 requires a non-empty column[] POST parameter for all modes…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-g3mx-8jm6-rc85
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-34382 Advisory: Admidio has Missing CSRF Protections on Custom List Deletion in mylist_function.php IDs: CVE-2026-34382, GHSA-g3mx-8jm6-rc85 Record: https://patchnext.com/advisories/cve-2026-34382 (revision 1, source checked 26 Oct 2026, 14:39 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 4.6) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: admidio/admidio 5.0.8. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist admidio/admidio: affected >= 5.0.0, <= 5.0.7; fixed in 5.0.8 ## Suggested inspection (read-only) - Packagist admidio/admidio: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on admidio/admidio. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-g3mx-8jm6-rc85 (GitHub-reviewed advisory GHSA-g3mx-8jm6-rc85 lists affected ranges: Packagist admidio/admidio >=5.0.0 <=5.0.7) Commands are suggestions: review each one before running it.
Loading voting…