# CVE-2026-34384: Admidio: Missing CSRF Protection on Registration Approval Actions

> Attackers can trick authorized users into approving pending registrations via crafted GET requests, bypassing manual approval workflows.

- **Severity:** Medium 4.5 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:H/A:N`)
- **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:** 31 Mar 2026
- **Updated:** 1 Apr 2026
- **Also known as:** GHSA-ph84-r98x-2j22

## What is CVE-2026-34384?

CVE-2026-34384 is a medium-severity vulnerability in admidio, published on 31 Mar 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Admidio is an open-source user management solution. Prior to version 5.0.8, the create_user, assign_member, and assign_user action modes in modules/registration.php approve pending user registrations via GET request without validating a CSRF token. Unlike the delete_user mode in the same file (which correctly validates the token), these three approval actions read their parameters from $_GET and perform irreversible state changes without any protection. An attacker who has submitted a pending registration can extract their own user UUID from the registration confirmation email URL, then trick any user with the rol_approve_users right into visiting a crafted URL that automatically approves the registration. This bypasses the manual registration approval workflow entirely. This issue has been patched in version 5.0.8.

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

## Which versions are affected by CVE-2026-34384?

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 | 5.0.8 |
| `admidio/admidio` | Packagist | All versions | 5.0.8 |

Products: Admidio Admidio.

## How do I fix CVE-2026-34384?

Upgrade admidio/admidio to 5.0.8 or later.

## Is CVE-2026-34384 being exploited?

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

## Other vulnerabilities in admidio

- [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-2026-34384 and fix it if it is affected.

What it is: CVE-2026-34384 is a medium-severity vulnerability in admidio, published on 31 Mar 2026. 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-2026-34384 exists.

Affected packages and fixed versions:
- admidio/admidio (Packagist): affected all versions; fixed in 5.0.8
- admidio/admidio (Packagist): affected all versions; fixed in 5.0.8

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-2026-34384/ (Markdown: https://insights.sbomify.com/CVE-2026-34384/index.md)
```

## Sources

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

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