PatchSiren cyber security CVE debrief
CVE-2026-9579 JeecgBoot CVE debrief
A low-severity improper access control vulnerability in JeecgBoot versions up to 3.9.1 allows authenticated remote attackers to manipulate the userIdentity parameter in the /sys/user/login/setting/userEdit endpoint's user.getUsername function. The vulnerability, published 2026-05-26, has a CVSS 4.0 score of 2.1 (LOW severity) and has been publicly disclosed with available exploit details. The vendor has released version 3.9.2 to address this issue.
- Vendor
- JeecgBoot
- Product
- JeecgBoot
- CVSS
- LOW 2.1
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-05-26
- Original CVE updated
- 2026-05-27
- Advisory published
- 2026-05-26
- Advisory updated
- 2026-05-27
Who should care
Organizations running JeecgBoot versions 3.9.1 or earlier with authenticated user access to the SysUser management functionality should prioritize upgrading to version 3.9.2.
Technical summary
The vulnerability exists in the user.getUsername function within the SysUser component of JeecgBoot, specifically at the /sys/user/login/setting/userEdit endpoint. An authenticated attacker can remotely manipulate the userIdentity argument to bypass intended access controls. The attack complexity is low, requires no user interaction, and can be executed over the network. The vulnerability results in limited impacts to confidentiality, integrity, and availability. The exploit has been made public, increasing the risk of attempted exploitation.
Defensive priority
routine
Recommended defensive actions
- Upgrade JeecgBoot to version 3.9.2 or later
- Review access controls on /sys/user/login/setting/userEdit endpoint
- Audit user privilege assignments for improper configurations
- Monitor for anomalous requests to SysUser component endpoints
Evidence notes
Vulnerability affects JeecgBoot ≤3.9.1 via userIdentity parameter manipulation in SysUser component. CWE-266 (Incorrect Privilege Assignment) and CWE-284 (Improper Access Control) identified. Public exploit availability confirmed. Fix released in v3.9.2.
Official resources
public