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

CVE-2026-108874: JeecgBoot Authorization Bypass Vulnerability

CVE-2026-108874 is an authorization bypass flaw in JeecgBoot through version 3.9.5 that lets authenticated users manipulate department head assignments. This post covers the technical details, affected versions, impact, and mitigation.

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

CVE-2026-108874 is a missing authorization vulnerability [CWE-862] in JeecgBoot versions through 3.9.5. The flaw resides in the PUT /sys/user/changeDepartChargePerson endpoint, which fails to verify that the caller has administrative rights over the target department. Any authenticated user can submit arbitrary userId, department id, and status values to assign or revoke department head roles. Successful exploitation lets a low-privileged attacker promote any account to department head, broadening department-scoped data access, or demote legitimate heads to disrupt operations.

Critical Impact

Low-privileged authenticated users can manipulate department leadership assignments across the application, enabling horizontal privilege escalation and unauthorized broadening of department-scoped data visibility.

Affected Products

  • JeecgBoot versions through 3.9.5
  • jeecg-module-system component (SysUserController.java)
  • Deployments exposing the /sys/user/changeDepartChargePerson endpoint to authenticated users

Discovery Timeline

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

Technical Details for CVE-2026-108874

Vulnerability Analysis

The vulnerability stems from an authorization check that is entirely absent on the changeDepartChargePerson controller method in SysUserController.java. The endpoint accepts a request body containing userId, department id, and status, then writes the mapping directly to the department-charge relationship. Because the handler only requires an authenticated session, any user token issued by the platform can invoke it.

This is a horizontal privilege escalation path. By flipping the department head flag on an attacker-controlled account, the attacker inherits the broader data visibility that JeecgBoot grants to department leaders. The same primitive can be used in reverse to demote a legitimate head and interfere with workflows that rely on charge-person assignments.

The issue is scoped to integrity of role assignments; confidentiality and availability impact are indirect, surfacing when expanded department-scoped views expose additional records or when demotions disrupt approval chains.

Root Cause

The root cause is a missing authorization check [CWE-862] in the controller logic referenced at SysUserController.java lines 2007-2011. The method relies on authentication alone and does not confirm that the caller holds a role entitled to modify department leadership for the targeted id.

Attack Vector

Exploitation requires a valid low-privileged session and network reachability to the JeecgBoot API. The attacker issues a PUT request to /sys/user/changeDepartChargePerson with chosen userId, department id, and status fields. A public proof-of-concept script demonstrating the request flow is published at the GitHub PoC Repository.

For controller-level context, see the vulnerable handler in the GitHub Source Code and the coordinated writeup in the VulnCheck Security Advisory.

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-108874

Indicators of Compromise

  • HTTP PUT requests to /sys/user/changeDepartChargePerson originating from non-administrative user sessions.
  • Unexpected modifications to sys_depart or related department-charge tables outside normal administrative workflows.
  • Audit log entries showing department head assignments made by users without an administrative role.

Detection Strategies

  • Enable application-level audit logging for all PUT /sys/user/changeDepartChargePerson calls and correlate the caller role against the modification.
  • Alert when the same account is granted department head status for multiple unrelated departments in a short window.
  • Review web access logs for authenticated low-privileged accounts invoking department management endpoints.

Monitoring Recommendations

  • Baseline normal administrative traffic patterns for /sys/user/* endpoints and flag deviations.
  • Monitor downstream database tables tracking department heads for off-hours or bulk changes.
  • Forward JeecgBoot application logs to a centralized analytics platform to retain evidence of role manipulation.

How to Mitigate CVE-2026-108874

Immediate Actions Required

  • Restrict network exposure of the JeecgBoot management API to trusted administrative networks until a patched release is applied.
  • Review the department head assignments in sys_depart and revert any unauthorized changes.
  • Rotate session tokens for accounts suspected of exploiting the endpoint and audit their recent activity.

Patch Information

No vendor-published fixed version is referenced in the current advisory. The VulnCheck Security Advisory confirms the issue affects JeecgBoot through 3.9.5. Monitor the JeecgBoot repository for a release that adds an authorization check to the changeDepartChargePerson handler and upgrade promptly when available.

Workarounds

  • Place a reverse proxy or API gateway rule in front of JeecgBoot that limits PUT /sys/user/changeDepartChargePerson to administrator source identities.
  • Apply a local patch adding a server-side role check (for example, an @RequiresRoles("admin") style annotation) on the controller method before redeploying.
  • Temporarily disable the endpoint if department-head assignment workflows can be performed through an alternative administrative path.
bash
# Example API gateway rule (nginx) to restrict the vulnerable endpoint
location = /sys/user/changeDepartChargePerson {
    limit_except PUT { deny all; }
    allow 10.0.0.0/24;   # admin 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.