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

CVE-2026-108870: JeecgBoot Privilege Escalation Vulnerability

CVE-2026-108870 is a privilege escalation flaw in JeecgBoot allowing low-privileged users to modify role data rules and bypass row-level security filters. This post explains its impact, affected versions, and mitigation steps.

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

CVE-2026-108870 is a missing authorization vulnerability [CWE-862] in JeecgBoot versions through 3.9.5. The flaw resides in the SysRoleController.saveDatarule handler, which fails to verify that the requesting user has permission to modify role data rules. Low-privileged authenticated users can send crafted requests containing permissionId, roleId, and dataRuleIds parameters to overwrite the data_rule_ids field. This action clears row-level filters, widens readable records, or alters filtering applied to other roles. The vulnerability affects the JeecgBoot low-code platform and enables unauthorized tampering with role-based data access controls.

Critical Impact

Authenticated users with low privileges can modify data rules for arbitrary roles, bypassing row-level security filters and exposing records that should remain restricted.

Affected Products

  • JeecgBoot through version 3.9.5
  • jeecg-module-system component
  • SysRoleControllersaveDatarule endpoint

Discovery Timeline

  • 2026-10-11 - CVE-2026-108870 published to NVD
  • 2026-10-14 - Last updated in NVD database

Technical Details for CVE-2026-108870

Vulnerability Analysis

The vulnerability exists in the SysRoleController.saveDatarule handler within the jeecg-system-biz module. The handler accepts permissionId, roleId, and dataRuleIds parameters from HTTP POST requests but does not enforce authorization checks on the caller. Any authenticated session, including low-privileged accounts, can invoke the endpoint and overwrite data_rule_ids for roles the user does not own.

Row-level data rules in JeecgBoot restrict which database records a given role can read. By submitting an empty or crafted dataRuleIds value, attackers can clear filters entirely, exposing records that were previously hidden. Alternatively, attackers can assign restrictive rules to other roles to disrupt their access.

The impact extends to data confidentiality and integrity within the affected tenant. Because JeecgBoot is widely deployed as a backend scaffolding platform for enterprise applications, the exposed records can include business, personnel, or operational data governed by role-level filters.

Root Cause

The root cause is a missing authorization check in the controller method. The handler relies on authentication alone and does not validate whether the authenticated principal has administrative privileges over role configuration or the specific roleId targeted by the request. This matches the pattern described by CWE-862: Missing Authorization.

Attack Vector

The attack vector is network-based and requires low privileges. An attacker authenticates with any valid user account, then issues an HTTP POST request to the saveDatarule endpoint. The request body carries the target permissionId, roleId, and dataRuleIds. The server processes the write without verifying the caller's authority over the specified role.

A proof-of-concept script demonstrating the request flow is published in the GitHub PoC Repository. The vulnerable source lines are documented in the JeecgBoot GitHub source file.

Detection Methods for CVE-2026-108870

Indicators of Compromise

  • POST requests to the saveDatarule endpoint originating from accounts that are not members of the system administrator role.
  • Database audit entries showing unexpected changes to the data_rule_ids column in the role-permission mapping tables.
  • Sudden expansion of records returned by role-filtered queries for users whose permissions have not legitimately changed.

Detection Strategies

  • Enable application-layer logging on all SysRoleController endpoints and correlate caller identity with the targeted roleId.
  • Baseline normal administrative activity on data rule configuration and alert on writes performed outside expected maintenance windows.
  • Deploy a web application firewall rule that inspects POST requests to the saveDatarule path and blocks requests lacking administrator session attributes.

Monitoring Recommendations

  • Monitor database change-data-capture streams for writes to role data rule tables and attribute each change to a specific authenticated user.
  • Alert on repeated 2xx responses to role management endpoints from the same low-privileged account within short time windows.
  • Review access logs after each JeecgBoot upgrade to confirm the vulnerable endpoint has been patched or protected.

How to Mitigate CVE-2026-108870

Immediate Actions Required

  • Upgrade JeecgBoot to a version later than 3.9.5 that includes an authorization check on the saveDatarule handler.
  • Restrict network access to JeecgBoot administrative endpoints so that only trusted internal networks can reach /sys/role/* routes.
  • Audit existing data_rule_ids assignments and restore the intended row-level filters for any role that was modified without authorization.

Patch Information

Refer to the VulnCheck Security Advisory for the current remediation status and upstream fix references. Review the JeecgBoot source repository for the latest release that enforces role-level authorization on the saveDatarule endpoint.

Workarounds

  • Apply a reverse-proxy rule that requires an administrator role claim before forwarding requests to saveDatarule.
  • Implement a server-side filter or interceptor that validates the authenticated principal has permission to modify the targeted roleId before the controller executes.
  • Rotate credentials for low-privileged accounts and review audit logs for prior exploitation attempts.
bash
# Example nginx location block restricting access to the vulnerable endpoint
location ~ ^/jeecg-boot/sys/role/saveDatarule$ {
    allow 10.0.0.0/8;
    deny all;
    proxy_pass http://jeecg_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.