Superagi EUVD-2026-23721

Exploitation requires a valid, authenticated user session or credentials (PR:L per CVSS vector). The vulnerability affects the update_user function when called with a manipulated user_id parameter that differs from the authenticated user's own ID. The application must be deployed in a configuration where multiple users exist (typical production setup). No special non-default configuration is required; standard multi-user installations are vulnerable. The limiting factor is the authentication requirement: unauthenticated remote attackers cannot exploit this. However, any user account - including low-privilege or guest accounts if the application supports such roles - can exploit the vulnerability to modify other user accounts.

CVSS 5.4 with network vector (AV:N), low complexity (AC:L), and low privilege requirement (PR:L) indicates moderate but genuine risk. The CVSS environmental factor E:P confirms public exploit availability. CVSS Scope Unchanged (S:U) suggests impact remains within the same security boundary, but the vulnerability still enables integrity and availability impacts (I:L, A:L) - specifically unauthorized modification and potential disruption of other user accounts. The low privilege requirement is the critical limiting factor: exploitation requires valid authentication, narrowing the attacker pool to users with legitimate access. However, any authenticated user can exploit this, making it dangerous in open-registration deployments. The lack of vendor response and public exploit availability elevate real-world risk despite the moderate CVSS score. This is NOT a high-CVSS-but-low-risk issue; it is a realistic, immediately exploitable authorization flaw in production systems.

An authenticated user with valid credentials logs into SuperAGI. The attacker observes that the user update API endpoint accepts a user_id parameter. By modifying this parameter to another user's ID (e.g., changing from /api/update_user?user_id=123 to /api/update_user?user_id=456), the attacker submits a request to modify that other user's email, password, or role. The server fails to verify authorization and applies the changes to the target user's account, causing denial of service or unauthorized privilege escalation if role fields can be modified. A public exploit script available on GitHub (gist.github.com/YLChen-007) automates this by iterating through user IDs to enumerate and modify multiple accounts.