CVE-2026-41662
Privilege Escalation in Admidio User Management
Publication date: 2026-05-07
Last updated on: 2026-05-07
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| admidio | admidio | to 5.0.9 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-754 | The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows any administrator to remove the last remaining administrator, locking the system out of administrative access. This can lead to a denial of administrative control and potentially impact system availability.
While the CVE description and resources do not explicitly mention compliance with standards such as GDPR or HIPAA, the loss of administrative access could hinder the ability to manage user data and enforce security policies, which are critical for compliance with such regulations.
In particular, inability to administer the system may delay or prevent timely responses to data subject requests, security incident management, or enforcement of access controls, all of which are important for regulatory compliance.
Can you explain this vulnerability to me?
This vulnerability exists in Admidio versions 5.0.8 and earlier, where the function Role::stopMembership() does not check if removing a user from the administrator role would leave the system with zero administrators.
Because of this, any administrator can remove the last remaining other administrator, effectively locking everyone out of administrative access to the system.
The older deprecated function Membership::stopMembership() had a safety check to prevent this, but the current code bypasses that check.
Exploitation does not require simultaneous requests; sequential removals can achieve the same lockout.
How can this vulnerability impact me? :
The main impact of this vulnerability is that an attacker with administrator privileges can remove all other administrators, leaving the system with no administrative access.
This results in a denial of service condition where no one can perform administrative tasks or manage the system.
Recovery from this state requires direct database manipulation, which may be difficult or impossible in some hosting environments, such as shared hosting.
The vulnerability has a moderate CVSS score of 5.2, with a high impact on availability and low impact on integrity.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves the removal of the last remaining administrator from the Admidio system, which results in a lockout of all administrative access.
Detection would involve checking the current number of administrators in the system and verifying if any administrator accounts have been removed recently, especially if the system is locked out of administrative access.
Since the exploit does not require concurrent requests and can be done sequentially, monitoring administrative role changes and removals in logs or the database is essential.
Specific commands are not provided in the resources, but administrators can query the database to count the number of users assigned to the administrator role to detect if zero administrators remain.
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade Admidio to version 5.0.9 or later, where this vulnerability has been patched.
Until the upgrade can be applied, administrators should avoid removing administrator accounts if it might leave zero administrators in the system.
If the system is already locked out due to this vulnerability, recovery requires direct database manipulation to restore administrator accounts, which may be difficult in some hosting environments.