CVE-2026-8127
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA vulnerability has been found in eladmin up to 2.7. Impacted is the function checkLevel of the file /rest/UserController.java of the component Users API Endpoint. Such manipulation leads to improper access controls. The attack can be executed remotely. The exploit has been disclosed to the public and may be used. The project was informed of the problem early through an issue report but has not responded yet.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceImproper access control vulnerability in eladmin up to v2.7 in the Users API endpoint. The checkLevel function in /rest/UserController.java fails to properly enforce authorization checks, allowing attackers to potentially bypass role-based access restrictions on user management operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify eladmin versionCheck the application version file, pom.xml, build configuration, or application startup logs for the eladmin version numberAffected if Installed version is v2.7 or earlier (any version up to and including v2.7)
-
Confirm Users API endpoint is exposedVerify that the /rest/UserController endpoint is accessible in the deployed application (check application.yml/yaml routing config or attempt a test request)Affected if The /rest/UserController endpoint is reachable without authentication or with low-privilege credentials
-
Test authorization bypass on user managementSend a request to the Users API endpoint (e.g., GET /rest/user or /rest/user/list) with a low-privilege or non-admin account, or attempt to manipulate request parameters to bypass the checkLevel functionAffected if The API returns user data or allows user management operations without proper role validation (e.g., returns admin data when requesting as a regular user)
-
Inspect checkLevel function implementationReview the source code of /rest/UserController.java and locate the checkLevel method to confirm it lacks proper role validation logic (search for missing role checks or conditional statements that can be bypassed)Affected if The checkLevel function does not validate user roles before returning sensitive user data or performing privileged operations
You are affected if you are running eladmin version 2.7 or earlier AND the /rest/UserController endpoint is exposed, with the checkLevel function failing to enforce role-based access controls.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedFix the checkLevel function to properly validate user permissions/roles before allowing access to user data. Implement role-based access control (RBAC) checks that cannot be bypassed through manipulation of API requests.
latest stable eladmin release after version 2.7
- Identify the current eladmin version in use by checking the application's pom.xml or build configuration file
- Review the application's dependencies to confirm eladmin version
- Upgrade eladmin to the latest stable release that includes the fix for the checkLevel function privilege escalation vulnerability
- After upgrading, verify that the Users API endpoint properly enforces privilege checks in the checkLevel function
- Test user role assignments and access controls to confirm the vulnerability is remediated
- Monitor the project's official GitHub repository for any security advisories or patch releases
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8127 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8127 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data