Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-108891 Overview
CVE-2026-108891 is a missing authorization vulnerability in JeecgBoot through version 3.9.5. The flaw resides in the getUserDetailByUserId handler within SysUserController. Any authenticated user, regardless of role, can supply an arbitrary userId parameter and retrieve detailed account information belonging to other users. Exposed fields include real names, usernames, email addresses, phone numbers, birthdays, employee numbers, department paths, and posts. The weakness is tracked as [CWE-862] Missing Authorization.
Critical Impact
Low-privileged authenticated attackers can enumerate and harvest personally identifiable information (PII) for every user in a JeecgBoot deployment, enabling follow-on phishing, social engineering, and targeted account takeover campaigns.
Affected Products
- JeecgBoot versions through 3.9.5
- jeecg-module-system component (SysUserController)
- Deployments exposing the /sys/user/getUserDetailByUserId endpoint to authenticated users
Discovery Timeline
- 2026-10-11 - CVE-2026-108891 published to NVD
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-108891
Vulnerability Analysis
JeecgBoot is a low-code development platform built on Spring Boot. The SysUserController.getUserDetailByUserId handler accepts a userId request parameter and returns a populated user detail object from the backend repository. The handler enforces authentication through the standard Shiro filter chain but omits an authorization check verifying that the caller is either the owner of the requested record or holds an administrative role.
As a result, any user who can obtain a session token, including freshly registered or low-privilege accounts, can iterate over user identifiers and extract sensitive profile data. The response payload includes direct identifiers and organizational metadata suitable for crafting convincing spear-phishing lures or mapping internal hierarchies.
Root Cause
The root cause is the absence of a server-side authorization decision in the handler. The method relies on authentication alone and does not compare the submitted userId against the authenticated principal or check for a privileged role. The vulnerable code path is documented in the upstream repository at SysUserController.java lines 1034-1047.
Attack Vector
Exploitation requires network access to the application and valid credentials for any account. The attacker authenticates, obtains a session or token, and issues HTTP requests to the getUserDetailByUserId endpoint while varying the userId parameter. A public proof of concept demonstrating automated enumeration is available at the GitHub PoC Implementation. See the VulnCheck Advisory for JeecgBoot for additional context.
Detect Identity Attacks the Moment Authentication Fails
Singularity™ Identity surfaces credential misuse, lateral movement, and privilege escalation in real time, so you can contain the breach before it spreads.
Stop Identity AttacksDetection Methods for CVE-2026-108891
Indicators of Compromise
- High volumes of requests to /sys/user/getUserDetailByUserId from a single authenticated session within a short interval
- Sequential or scripted enumeration patterns across the userId query parameter
- Low-privileged accounts accessing user records outside their own department scope
Detection Strategies
- Deploy application-layer logging that captures the userId parameter and the authenticated principal for every call to the SysUserController endpoints
- Alert when a single session queries more than a threshold of distinct userId values within a rolling time window
- Correlate access logs against role data to flag non-administrative accounts requesting records they do not own
Monitoring Recommendations
- Forward JeecgBoot application and web server logs to a centralized analytics platform for query and retention
- Baseline normal usage of the user detail endpoint by role, then alert on deviations
- Monitor newly created accounts for immediate access to user enumeration endpoints, a common post-registration abuse pattern
How to Mitigate CVE-2026-108891
Immediate Actions Required
- Inventory JeecgBoot deployments and identify any instance running version 3.9.5 or earlier
- Restrict network exposure of the administrative API surface to trusted internal networks where feasible
- Review authentication logs for unexpected enumeration activity against getUserDetailByUserId
- Rotate credentials and session tokens for any account showing anomalous access patterns
Patch Information
As of the NVD publication date, no fixed version has been documented in the enriched advisory data. Monitor the VulnCheck Advisory for JeecgBoot and the upstream JeecgBoot repository for an official patch addressing the missing authorization check in SysUserController.getUserDetailByUserId.
Workarounds
- Add a server-side authorization filter that compares the requested userId to the authenticated principal and rejects mismatched requests unless the caller holds an administrative role
- Place the getUserDetailByUserId endpoint behind a reverse-proxy allow list limited to administrative subnets
- Reduce the response schema to omit PII fields such as phone numbers, birthdays, and employee numbers until a patch is applied
- Rate-limit requests to the user detail endpoint to slow automated enumeration
# Example NGINX reverse-proxy restriction for the vulnerable endpoint
location = /jeecg-boot/sys/user/getUserDetailByUserId {
allow 10.0.0.0/8; # internal admin network
deny all;
proxy_pass http://jeecgboot_upstream;
}
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

