Admidio's CSRF in registration send_login mode resets arbitrary user passwords

Exploitation

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

CVSS

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

EPSS

• CVE-2026-47228: 0.16% estimated exploitation activity in the next 30 days; percentile 5.33 (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 modules/registration.php mode sendlogin regenerates a random password for useruuidassigned, stores its bcrypt hash in admusers.usrpassword, and emails the cleartext to that user. Every other state-changing mode in the same file (assignmember, assignuser, deleteuser, createuser) calls SecurityUtils::validateCsrfToken($POST['admcsrftoken']) first; the sendlogin branch does not. A page visited by a registration-administrator can issue the request as a top-level navigation, the browser sends the admin's SameSite=Lax cookies, and the server resets the chosen user's password without any further interaction from the admin. Details Vulnerable Code modules/registration.php:124-138: The four sibling branches all begin with SecurityUtils::validateCsrfToken($POST['admcsrftoken']); — for example deleteuser at lines 110-118: User::sendNewPassword() (src/User/Entity/User.php) calls setPassword(PasswordUtils::generatePassword()) and persists the new hash before the email is queued; the…

Published by the source

29 May 2026, 21:58 UTC

Last modified by the source

29 May 2026, 21:58 UTC

Source last checked

26 Oct 2026, 14:48 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-mx25-j3rc-6w2w

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

# Patch Next advisory brief: CVE-2026-47228

Advisory: Admidio's CSRF in registration `send_login` mode resets arbitrary user passwords
IDs: CVE-2026-47228, GHSA-mx25-j3rc-6w2w
Record: https://patchnext.com/advisories/cve-2026-47228 (revision 1, source checked 26 Oct 2026, 14:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.2)
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.10. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist admidio/admidio: affected <= 5.0.9; fixed in 5.0.10

## 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-mx25-j3rc-6w2w (GitHub-reviewed advisory GHSA-mx25-j3rc-6w2w lists affected ranges: Packagist admidio/admidio >=0 <=5.0.9)

Commands are suggestions: review each one before running it.