CVE-2026-30927: Admidio: Event participation IDOR - non-leaders can register other users for events via user_uuid parameter

Published Mar 9, 2026
·
Updated

Vulnerability

In modules/events/eventsfunction.php, the event participation logic allows any user who can participate in an event to register OTHER users by manipulating the useruuid GET parameter.

Line 47: $getUserUuid = admFuncVariableIsValid($GET, 'useruuid', 'uuid', ...) Line 424: if ($event->possibleToParticipate() || $participants->isLeader($gCurrentUserId))

The condition uses || (OR), meaning if possibleToParticipate() returns true (event is open for participation), ANY user - not just leaders - can specify a different useruuid and register/cancel participation for that user.

The code then operates on $user->getValue('usrid') (the target user from useruuid) rather than the current user.

Impact - Register unwilling users for events (potential harassment/spam) - Cancel other users' event participation - Manipulate event participant counts and comments - If events have participation limits, fill slots with unwanted registrations

Fix For non-leader users, force useruuid to the current user: php if (!$participants->isLeader($gCurrentUserId)) { $getUserUuid = $gCurrentUser->getValue('usruuid'); }

Other sources

Admidio is an open-source user management solution. Prior to 5.0.6, in modules/events/eventsfunction.php, the event participation logic allows any user who can participate in an event to register OTHER users by manipulating the useruuid GET parameter. The condition uses || (OR), meaning if possibleToParticipate() returns true (event is open for participation), ANY user - not just leaders - can specify a different useruuid and register/cancel participation for that user. The code then operates on $user->getValue('usrid') (the target user from useruuid) rather than the current user. This vulnerability is fixed in 5.0.6.

MITRE

Affected Software

2 affected componentsFixes available
composer/admidio/admidio<5.0.6
5.0.6
Admidio Admidio<5.0.6

Event History

Mar 9, 2026
Advisory Published
via GitHub·07:45 PM
Data Sourced
via GitHub·07:45 PM
DescriptionWeaknessAffected Software
CVE Published
via MITRE·11:03 PM
Data Sourced
via MITRE·11:03 PM
DescriptionWeakness
Mar 10, 2026
Data Sourced
via NVD·05:40 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:40 PM
RemedyAffected Software
Nov 13, 58169
Event
via FIRST·08:38 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-30927?

CVE-2026-30927 has a high severity rating due to an authentication bypass allowing unauthorized event registrations.

2

How do I fix CVE-2026-30927?

To fix CVE-2026-30927, update Admidio to version 5.0.6 or later to address the vulnerability.

3

What systems are affected by CVE-2026-30927?

CVE-2026-30927 affects all versions of Admidio prior to 5.0.6.

4

What is the impact of CVE-2026-30927?

The impact of CVE-2026-30927 allows non-leader users to register other users for events, undermining user permissions.

5

How can I determine if my Admidio installation is vulnerable to CVE-2026-30927?

You can determine vulnerability by checking if your Admidio version is below 5.0.6.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203