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-108678 Overview
CVE-2026-108678 is a missing authorization vulnerability [CWE-862] in JeecgBoot through version 3.9.5. The flaw resides in the queryUserRoles handler of SystemApiController, which fails to verify that the requesting user owns the target account. Any authenticated low-privileged user can issue a GET request to /sys/api/queryUserRoles with an arbitrary username parameter and retrieve that account's role codes. Attackers use this disclosure to enumerate role assignments across the tenant and identify administrator accounts for follow-on attacks.
Critical Impact
Authenticated attackers can enumerate role assignments for any JeecgBoot user, exposing administrator accounts and accelerating privilege-escalation campaigns.
Affected Products
- JeecgBoot versions up to and including 3.9.5
- jeecg-module-system component (SystemApiController.java)
- Deployments exposing the /sys/api/queryUserRoles endpoint to authenticated users
Discovery Timeline
- 2026-10-10 - CVE-2026-108678 published to NVD
- 2026-10-14 - Last updated in NVD database
Technical Details for CVE-2026-108678
Vulnerability Analysis
The vulnerability sits in the queryUserRoles method of SystemApiController within the jeecg-module-system module. The handler accepts a username query parameter and returns the role codes associated with that account. It performs no check comparing the requested username against the authenticated principal, and it does not require administrator privileges. As a result, authorization enforcement collapses to "any valid session," which violates the principle of least privilege.
An authenticated attacker iterates likely usernames or walks a known user list, calling the endpoint for each candidate. The response reveals role codes such as admin, superadmin, or tenant-specific administrative identifiers. This mapping of users to privileged roles turns a low-value foothold into a precise target list for credential stuffing, phishing, or chained exploitation.
Root Cause
The queryUserRoles handler omits an ownership or role check before returning role data for the supplied username. The controller treats the endpoint as a general-purpose lookup rather than a self-service query, and the framework's session filter only validates authentication, not authorization. See the upstream SystemApiController source for the vulnerable code path.
Attack Vector
Exploitation requires a valid session on the target JeecgBoot instance. The attacker sends GET /sys/api/queryUserRoles?username=<target> with their session token. The server responds with the role codes assigned to <target>. By scripting the request across a username wordlist, the attacker builds a complete map of role assignments and locates administrator accounts. A proof-of-concept script is published in the AnkesKasty cve-request-poc repository.
Detection Methods for CVE-2026-108678
Indicators of Compromise
- Repeated authenticated GET requests to /sys/api/queryUserRoles with varying username values from a single session or IP
- Access to queryUserRoles by accounts that have no legitimate administrative function
- Short-interval enumeration patterns against the /sys/api/ path tree
Detection Strategies
- Alert on any single session issuing more than a small threshold of queryUserRoles requests within a rolling window
- Correlate queryUserRoles access with subsequent authentication attempts against the usernames queried
- Baseline normal callers of /sys/api/queryUserRoles and flag deviations by account, source IP, or user agent
Monitoring Recommendations
- Forward JeecgBoot application logs and reverse-proxy access logs to a centralized analytics platform for query and alerting
- Enable per-endpoint rate metrics on /sys/api/queryUserRoles and track response payload sizes
- Review audit trails for role-code lookups tied to accounts that later attempt privilege-sensitive actions
How to Mitigate CVE-2026-108678
Immediate Actions Required
- Restrict network access to /sys/api/queryUserRoles through reverse-proxy or WAF rules until a patched release is deployed
- Require that queryUserRoles only return data when the requested username matches the authenticated principal, or when the caller holds an administrative role
- Rotate credentials for administrator accounts whose role assignments may have been enumerated
Patch Information
No fixed version is listed in the NVD entry at publication. Monitor the JeecgBoot repository and the VulnCheck advisory for a vendor-supplied fix and upgrade beyond version 3.9.5 once available.
Workarounds
- Add a server-side authorization filter that compares the username parameter against the session principal before invoking the handler
- Block or require administrator role for /sys/api/queryUserRoles at the API gateway or ingress layer
- Remove or disable the queryUserRoles endpoint if the deployment does not rely on it for application functionality
# Example NGINX rule restricting the endpoint to an internal management network
location = /sys/api/queryUserRoles {
allow 10.0.0.0/8;
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

