Skip to main content
Vulnerability Database/CVE-2026-108627

CVE-2026-108627: JeecgBoot Authorization Bypass Vulnerability

CVE-2026-108627 is an authorization bypass vulnerability in JeecgBoot through version 3.9.5 that allows authenticated users to access role data rules without proper authorization. This article covers technical details, affected versions, security impact, and mitigation strategies.

Published:

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-108627 Overview

CVE-2026-108627 is a missing authorization vulnerability [CWE-862] in JeecgBoot through version 3.9.5. The flaw resides in the loadDatarule handler of SysRoleController, which fails to enforce role-based access controls on the data-rule lookup endpoint. Any authenticated user, regardless of privilege level, can issue a GET /sys/role/datarule/{permissionId}/{roleId} request and retrieve role data rules. Returned data includes rule names, columns, conditions, values, and bound rule identifiers for arbitrary roles. The exposure allows low-privileged accounts to enumerate access control logic that governs higher-privileged roles across the application.

Critical Impact

Low-privileged attackers can enumerate data rules bound to any role, exposing permission boundaries, filter columns, and condition values used for row-level access control.

Affected Products

  • JeecgBoot through version 3.9.5
  • jeecg-module-system component containing SysRoleController
  • Deployments exposing the /sys/role/datarule/{permissionId}/{roleId} endpoint

Discovery Timeline

  • 2026-10-10 - CVE-2026-108627 published to NVD
  • 2026-10-13 - Last updated in NVD database

Technical Details for CVE-2026-108627

Vulnerability Analysis

The vulnerability lives in the loadDatarule handler defined in SysRoleController.java of the jeecg-module-system module. The handler accepts a permissionId and roleId as path parameters and returns the associated data rules without validating whether the caller holds administrative privileges or belongs to the queried role. JeecgBoot's data-rule system drives row-level access control, so the response contains the exact SQL columns, operators, and values that gate restricted records. An attacker holding any valid session token can walk the role catalog and recover these rules in cleartext. The resulting disclosure maps the application's authorization model and highlights specific record filters that attackers can later target with injection, parameter tampering, or privilege-escalation chains.

Root Cause

The handler lacks an authorization check validating the caller's role membership or administrative permission before returning data-rule metadata. The controller relies solely on the authentication filter that confirms a valid session, treating any logged-in user as authorized to query internal role configuration. This is a classic missing-function-level access control defect tracked under CWE-862.

Attack Vector

Exploitation requires only a low-privileged authenticated session and network access to the JeecgBoot API. An attacker enumerates permissionId and roleId values and issues HTTP GET requests to /sys/role/datarule/{permissionId}/{roleId}. The server returns JSON containing the rule name, target column, condition operator, condition value, and the identifiers of rules bound to the role. The vulnerability does not permit data modification or code execution, but the leaked rule logic can inform follow-on attacks against the data layer. A proof-of-concept script demonstrating the request flow is published in the GitHub PoC repository, and the vulnerable handler is visible in the SysRoleController source.

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 Attacks

Detection Methods for CVE-2026-108627

Indicators of Compromise

  • Repeated GET requests to /sys/role/datarule/ from a single authenticated session enumerating sequential permissionId or roleId values.
  • Access to the datarule endpoint originating from user accounts that do not hold administrative or role-management permissions.
  • Spikes in 200 OK responses from the loadDatarule handler outside normal administrative workflows.

Detection Strategies

  • Instrument application logs to capture the authenticated principal, permissionId, and roleId for every /sys/role/datarule/ request.
  • Correlate datarule queries with the caller's assigned roles and alert when a user queries rules bound to roles they do not hold.
  • Baseline normal administrative access patterns and flag high-frequency enumeration from non-admin principals.

Monitoring Recommendations

  • Forward JeecgBoot API access logs to a centralized analytics platform for query-rate anomaly detection.
  • Track outbound disclosure of role metadata by inspecting response sizes and sensitive field names such as ruleColumn and ruleValue.
  • Review audit trails for sessions that query multiple role identifiers within short time windows.

How to Mitigate CVE-2026-108627

Immediate Actions Required

  • Restrict network access to the JeecgBoot administrative API using a reverse proxy or WAF rule that blocks /sys/role/datarule/ for non-administrative sessions.
  • Audit application logs for prior unauthorized access to the loadDatarule endpoint and identify accounts that enumerated role data.
  • Rotate or review data rules that reference sensitive columns or condition values if disclosure is suspected.

Patch Information

No fixed version is listed in the published advisory at the time of writing. Monitor the VulnCheck advisory for JeecgBoot and the upstream JeecgBoot repository for a patched release addressing versions after 3.9.5.

Workarounds

  • Add a server-side authorization check in SysRoleController.loadDatarule requiring the caller to hold the system administrator permission before returning data rules.
  • Deploy a gateway rule enforcing role-based access to /sys/role/datarule/{permissionId}/{roleId} until an official patch is applied.
  • Reduce the attack surface by limiting JeecgBoot console accounts to the smallest necessary set and disabling self-registration where possible.
bash
# Example reverse-proxy restriction (nginx) limiting datarule endpoint to internal admins
location ~ ^/sys/role/datarule/ {
    allow 10.0.0.0/24;   # admin management subnet
    deny all;
    proxy_pass http://jeecgboot_backend;
}

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

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.