CVE-2026-8127
Improper Access Control in eladmin Users API Endpoint
Publication date: 2026-05-08
Last updated on: 2026-05-08
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| eladmin | eladmin | to 2.7 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-284 | The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. |
| CWE-266 | A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2026-8127 is a vertical privilege escalation vulnerability in the eladmin system, specifically in the UserController.createUser endpoint.
The issue arises from a Mass Assignment vulnerability where a sub-administrator with user:add permissions can inject the isAdmin=true field when creating a new user, granting the new user super administrator privileges and bypassing the entire role-based access control system.
This happens because the isAdmin field is not checked by the checkLevel() method, which only validates role levels. The User entity is passed directly to the service layer without filtering, and the isAdmin field is persisted to the database.
When the new user logs in, the system grants them admin permissions, bypassing all subsequent permission checks.
The attack is executed by sending a POST request to /api/users with isAdmin set to true, which bypasses role-based restrictions and grants full administrative access.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows unauthorized privilege escalation by bypassing role-based access controls, potentially granting attackers full administrative access to the system.
Such improper access control can lead to unauthorized access to sensitive personal or protected health information, which may result in non-compliance with standards and regulations like GDPR and HIPAA that require strict access controls and protection of sensitive data.
Therefore, exploitation of this vulnerability could compromise data confidentiality and integrity, increasing the risk of regulatory violations and associated penalties.
How can this vulnerability impact me? :
This vulnerability allows a user with limited permissions (sub-administrator with user:add rights) to escalate their privileges to full administrator by creating a new user with isAdmin=true.
As a result, an attacker can gain unauthorized full administrative access to the system, bypassing all role-based access controls.
This can lead to unauthorized data access, modification, or deletion, and potentially complete control over the affected system.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for unauthorized users who have been granted super administrator privileges through the isAdmin field. Specifically, you can look for users in the database with the is_admin flag set to true who should not have such privileges.
Detection involves verifying if any user accounts have isAdmin=true set improperly, which indicates exploitation of the mass assignment vulnerability.
- Query the user database to find users with is_admin=true, for example using SQL: SELECT username, is_admin FROM users WHERE is_admin = true;
- Monitor HTTP POST requests to the /api/users endpoint for payloads containing isAdmin=true, which indicates attempts to exploit the vulnerability.
- Check application logs for creation of new users with elevated privileges or unusual role assignments.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include restricting the ability to set the isAdmin field during user creation or updates, especially for sub-administrators with user:add permissions.
Implement input validation and filtering to prevent mass assignment of the isAdmin field in the UserController.createUser endpoint.
Audit existing user accounts for unauthorized isAdmin=true flags and revoke such privileges where inappropriate.
Monitor and block suspicious POST requests to /api/users that include isAdmin=true.
Since the project has not yet responded with a patch, consider applying custom patches or workarounds to enforce role-based access control checks on the isAdmin field.