CVE-2026-6584
Received Received - Intake
Authorization Bypass in TransformerOptimus SuperAGI User Update Endpoint

Publication date: 2026-04-20

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability was found in TransformerOptimus SuperAGI up to 0.0.14. This vulnerability affects the function update_user of the file superagi/controllers/user.py of the component User Update Endpoint. The manipulation of the argument user_id results in authorization bypass. The attack may be performed from remote. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-20
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2026-04-20
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
transformeroptimus superagi to 0.0.14 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-285 The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows unauthorized users to update other users' profiles, including sensitive information such as names, emails, and passwords, leading to potential account takeover and privilege escalation.

Such unauthorized access and modification of personal and sensitive data can result in violations of data protection regulations like GDPR and HIPAA, which mandate strict controls over access to personal data and require protection against unauthorized disclosure or alteration.

Therefore, this vulnerability poses a significant risk to compliance with these standards by enabling unauthorized data access and modification, potentially leading to data breaches and regulatory penalties.


Can you explain this vulnerability to me?

This vulnerability exists in TransformerOptimus SuperAGI versions up to 0.0.14, specifically in the update_user function within the User Update Endpoint component. It allows an attacker to manipulate the user_id argument, resulting in an authorization bypass. This means an attacker can potentially perform actions or access data without proper permissions. The attack can be executed remotely, and a public exploit is available.


How can this vulnerability impact me? :

The vulnerability can lead to unauthorized access or modification of user data because of the authorization bypass. This could allow attackers to update user information without proper rights, potentially compromising user accounts or system integrity. Since the exploit is public and can be performed remotely, the risk of exploitation is higher.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by monitoring and testing the PUT /users/update/{user_id} API endpoint for improper authorization checks. Specifically, you can attempt to authenticate with a valid JWT token and issue a PUT request to update another user's profile by changing the user_id parameter in the URL.

A practical detection method is to use curl or similar HTTP clients to send crafted requests that try to update user information for user IDs other than the authenticated user.

  • Example curl command to test the vulnerability: curl -X PUT https://<target>/users/update/2 -H "Authorization: Bearer <your_jwt_token>" -H "Content-Type: application/json" -d '{"name":"test","email":"[email protected]","password":"newpassword"}'

If the request succeeds in updating another user's data without proper authorization, the vulnerability is present.


What immediate steps should I take to mitigate this vulnerability?

Immediate mitigation steps include restricting access to the user update endpoint and implementing proper authorization checks to ensure that users can only update their own profiles.

If possible, temporarily disable or restrict the PUT /users/update/{user_id} API endpoint until a patch or fix is applied.

Monitor logs for suspicious activity involving user updates, especially requests where the user_id does not match the authenticated user's ID.

Notify users to be vigilant for any unauthorized changes to their accounts and consider resetting passwords if unauthorized access is suspected.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart