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-108871 Overview
CVE-2026-108871 is a missing authorization vulnerability [CWE-862] in JeecgBoot through version 3.9.5. The flaw resides in the saveDatarule handler of SysDepartRoleController, which fails to verify whether the caller owns the department role being modified. Any authenticated low-privileged user can submit crafted permissionId, roleId, and dataRuleIds parameters to overwrite the data_rule_ids column for arbitrary department roles. The impact is tampering with row-level data access controls, which can widen or restrict visibility of records for other tenants or departments within the application.
Critical Impact
Authenticated users with minimal privileges can rewrite row-level data access rules for other department roles, breaking tenant isolation and leaking or hiding business records.
Affected Products
- JeecgBoot low-code platform versions up to and including 3.9.5
- Deployments exposing the jeecg-system-biz module endpoint POST /sys/sysDepartRole/saveDatarule
- Multi-tenant installations relying on department-role data rules for row-level security
Discovery Timeline
- 2026-10-11 - CVE-2026-108871 published to NVD
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-108871
Vulnerability Analysis
JeecgBoot uses department roles with associated data rules to enforce row-level filtering across modules. The saveDatarule endpoint in SysDepartRoleController persists the list of data rule identifiers that bind a role to a specific permission. The handler accepts permissionId, roleId, and dataRuleIds from the request body and updates the data_rule_ids column directly. It does not confirm that the caller belongs to the targeted department, holds administrative privileges on that role, or has write permission on the referenced permission entry. Any session with a valid token therefore passes the controller gate.
An attacker leveraging this weakness can rewrite data filters for finance, HR, or management roles. Rewriting the ruleset to a permissive value exposes rows that were previously isolated per department. Rewriting it to a restrictive or invalid value causes denial of visibility for legitimate users of that role. The behaviour maps directly to [CWE-862] Missing Authorization.
Root Cause
The controller method relies on authentication to reach the mapping but omits an ownership or role-scope check before executing the update. Business logic trusts the client-supplied roleId and permissionId without comparing them against the authenticated user's department membership or administrative role set.
Attack Vector
Exploitation requires network access to the JeecgBoot API and a valid low-privileged account. The attacker sends an HTTP POST request to /sys/sysDepartRole/saveDatarule with JSON values targeting another department's role. The server returns a success response and persists the new data_rule_ids, immediately changing data visibility for other users of that role. A proof-of-concept script demonstrating the request flow is published in the GitHub PoC Repository, and the vulnerable source range is documented in the JeecgBoot source on GitHub.
Detection Methods for CVE-2026-108871
Indicators of Compromise
- Unexpected UPDATE statements against the sys_depart_role_permission table modifying data_rule_ids outside of normal administrative workflows.
- HTTP POST requests to /sys/sysDepartRole/saveDatarule originating from accounts that do not hold department administrator roles.
- Audit log entries showing roleId or permissionId values that do not match the authenticated user's department scope.
Detection Strategies
- Review application access logs for calls to saveDatarule and correlate the caller's assigned department against the roleId parameter in the request body.
- Enable database-level auditing on sys_depart_role_permission and alert on changes to data_rule_ids performed by non-admin sessions.
- Baseline the normal rate of data rule modifications per account and flag any statistical anomalies.
Monitoring Recommendations
- Forward JeecgBoot application and database logs to a central analytics tier for correlation of authentication identity against role modification events.
- Monitor for repeated saveDatarule requests from a single session that iterate across multiple permissionId values, which indicates enumeration.
- Track row-level filter effectiveness through periodic reconciliation of expected versus actual row counts per role.
How to Mitigate CVE-2026-108871
Immediate Actions Required
- Restrict network reachability of the JeecgBoot administrative API so only trusted internal users can reach /sys/sysDepartRole/* endpoints.
- Audit existing sys_depart_role_permission.data_rule_ids values against a known-good baseline and revert unauthorized changes.
- Revoke or rotate credentials for low-privileged accounts that are not required for daily business operations.
Patch Information
No fixed version is listed in the NVD record at the time of publication. Consult the VulnCheck Security Advisory and the upstream JeecgBoot repository for updated releases beyond 3.9.5. Apply any vendor patch that introduces an authorization check binding roleId and permissionId to the authenticated caller's department scope.
Workarounds
- Deploy a reverse proxy or API gateway rule that blocks POST /sys/sysDepartRole/saveDatarule for all accounts outside an explicit administrator allowlist.
- Add a servlet filter or Spring interceptor that validates the caller's department ownership of the submitted roleId before the request reaches the controller.
- Temporarily disable self-service department role editing in the UI and route changes through a controlled administrative workflow.
# Example reverse proxy rule to restrict the vulnerable endpoint
location = /sys/sysDepartRole/saveDatarule {
allow 10.0.0.0/24; # administrator 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

