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-97060 Overview
CVE-2026-97060 is a Broken Object Level Authorization (BOLA) vulnerability in X-SpringBoot through version 6.0. The framework's user management endpoints fail to verify object ownership before processing modifications. Sub-administrators with user-management permissions can modify or delete any account, including the super administrator. Attackers can reset passwords, rebind roles, or delete users by sending crafted requests to POST /sys/user/update and POST /sys/user/delete. The flaw is tracked under CWE-639: Authorization Bypass Through User-Controlled Key.
Critical Impact
An authenticated sub-administrator can take over the super administrator account by resetting its password, resulting in full application compromise.
Affected Products
- X-SpringBoot through version 6.0
- SysUserController component (user management module)
- Deployments exposing /sys/user/update and /sys/user/delete endpoints
Discovery Timeline
- 2026-09-25 - CVE-2026-97060 published to NVD
- 2026-09-29 - Last updated in NVD database
Technical Details for CVE-2026-97060
Vulnerability Analysis
X-SpringBoot implements role-based access control at the endpoint level but does not enforce object-level authorization on individual user records. The SysUserController processes update and delete requests based solely on whether the caller holds the generic user-management permission. The controller never checks whether the target user ID falls within the caller's administrative scope or hierarchy.
This design allows any sub-administrator to act on any user object in the system. The super administrator account is not treated as a protected resource. An attacker holding limited user-management rights can escalate to full administrative control by submitting a password reset against the super administrator's user ID.
Root Cause
The root cause is missing authorization logic in the user update and delete handlers of SysUserController. The implementation at lines 190-216 of SysUserController.java validates the caller's permission token but does not compare the target user's role, tenant, or ownership against the caller's authority. This is a textbook CWE-639 condition where the server trusts a user-controlled key (the target user ID) without a reference check.
Attack Vector
Exploitation requires network access and a valid authenticated session with user-management permissions. The attacker enumerates or guesses the super administrator's user ID, then issues a POST /sys/user/update request supplying that ID with a chosen password and role assignment. The server processes the update and returns success. The attacker then authenticates as the super administrator.
A proof-of-concept script demonstrating cross-object BOLA against the user admin endpoint is published in the public PoC repository. The vulnerable controller source is available in the X-SpringBoot repository.
See the VulnCheck advisory for complete technical details.
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 AttacksDetection Methods for CVE-2026-97060
Indicators of Compromise
- Unexpected POST /sys/user/update or POST /sys/user/delete requests referencing the super administrator user ID or privileged account IDs.
- Password reset events on the super administrator account originating from a non-administrator session token.
- Role rebinding events where a sub-administrator modifies the role assignment of accounts outside their scope.
- New successful logins to privileged accounts shortly after an update request from a lower-privileged session.
Detection Strategies
- Review application and reverse-proxy logs for /sys/user/update and /sys/user/delete calls where the acting user and target user differ in privilege tier.
- Correlate user management API calls with the caller's role to flag cross-scope modifications.
- Alert on any modification to the super administrator account unless initiated by that account itself.
Monitoring Recommendations
- Forward X-SpringBoot audit logs to a centralized SIEM and build detections on target-user versus actor-role mismatches.
- Monitor authentication logs for password reset activity on administrative accounts followed by first-time logins from new source IP addresses.
- Track HTTP request volume to /sys/user/* endpoints and alert on anomalous bursts from a single session.
How to Mitigate CVE-2026-97060
Immediate Actions Required
- Restrict network exposure of X-SpringBoot administrative endpoints to trusted management networks only.
- Revoke user-management permissions from all accounts that do not strictly require them.
- Rotate the super administrator password and audit all existing user accounts for unauthorized role or credential changes.
- Review audit logs for prior exploitation of /sys/user/update and /sys/user/delete.
Patch Information
No vendor patch is referenced in the published advisory. The vulnerability affects X-SpringBoot through 6.0. Operators should monitor the X-SpringBoot GitHub repository for an upstream fix and apply authorization checks in SysUserController as a code-level remediation. The fix must verify that the acting user has authority over the target user ID before processing update or delete operations.
Workarounds
- Implement a server-side authorization filter in front of /sys/user/update and /sys/user/delete that rejects requests where the target user outranks the caller.
- Place the application behind a reverse proxy or WAF that enforces role-to-endpoint mappings and blocks cross-scope user ID parameters.
- Disable sub-administrator roles entirely until an upstream patch is available, limiting user management to the super administrator.
- Segment multi-tenant deployments so that sub-administrators cannot reach records outside their tenant through the shared endpoint.
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

