Admidio has Missing CSRF Protection on Registration Approval Actions

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-34384: 0.18% estimated exploitation activity in the next 30 days; percentile 7.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The createuser, assignmember, and assignuser action modes in modules/registration.php approve pending user registrations via GET request without validating a CSRF token. Unlike the deleteuser 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 rolapproveusers right into visiting a crafted URL that automatically approves the registration. This bypasses the manual registration approval workflow entirely. Details CSRF Protection Is Present for deleteuser but Absent for Approval Modes File: modules/registration.php, lines 90-128 The deleteuser mode validates the CSRF token (line 99), but the three approval modes do not: The three approval modes read both UUIDs exclusively from $GET (lines…

Published by the source

31 Mar 2026, 23:11 UTC

Last modified by the source

31 Mar 2026, 23:11 UTC

Source last checked

26 Oct 2026, 14:39 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-ph84-r98x-2j22

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-34384

Advisory: Admidio has Missing CSRF Protection on Registration Approval Actions
IDs: CVE-2026-34384, GHSA-ph84-r98x-2j22
Record: https://patchnext.com/advisories/cve-2026-34384 (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.5)
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.8; 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-ph84-r98x-2j22 (GitHub-reviewed advisory GHSA-ph84-r98x-2j22 lists affected ranges: Packagist admidio/admidio >=0 <5.0.8)

Commands are suggestions: review each one before running it.