Last updated
Was this helpful?
During a recent penetration testing engagement at , we uncovered a seemingly simple yet critically impactful vulnerability in a platform designed to sync WhatsApp with CRM systems. This platform allows teams to collaborate within workspaces, manage members, and work on projects together. The feature is central to the platform's core business logic, making it an ideal target for thorough security testing. What we discovered was a privilege escalation flaw that allowed us to elevate a member’s permissions to admin, ultimately leading to a full takeover of a workspace.
Our first step involved exploring the platform as a regular user with member-level permissions. We navigated to the member management page at , where we noticed something intriguing. The platform’s functionality heavily relied on REST API requests, and one request, in particular, caught our attention:
Invite member request:
Given the critical nature of member management in collaborative platforms, we suspected that access control might be a weak point. Typically, developers focus on front-end validations but may overlook the need for strict access control at the API level. With this in mind, we decided to test whether a member could elevate their privileges by modifying the role in an invitation request.
To our surprise, when we modified the role to "ADMIN" in the request while still authenticated as a regular member, the server accepted it without any complaints. The request looked like this:
And it worked! The member now had admin privileges. This success led us to wonder if we could take this further and fully exploit this vulnerability.
The next logical step was to see if we could manipulate the member's role directly through the API. Normally, role modification should be restricted to admins or workspace owners, but we suspected that server-side validation might be missing. So, we crafted the following request as a member:
This request was accepted by the server, effectively elevating our account to an admin role. Now, we had full control over the workspace.
A key question in exploiting this vulnerability was how an attacker could obtain the necessary workspace and user UUIDs. The answer was straightforward: another unprotected API endpoint provided all the required information. By simply sending a GET request, a member could retrieve the UUIDs of all users in the workspace:
With this information, the attacker could escalate their privileges to admin with ease.
Now that we had admin privileges, we wondered if we could remove the original workspace owner entirely. We attempted to delete the owner’s account from the workspace, example request:
Amazingly, the request succeeded, and we were now the sole admin of the workspace, having completely taken over the workspace from its original owner.
Strict Access Control: Ensure that API endpoints, especially those handling roles and permissions, are protected by server-side access control mechanisms.
UUID Protection: Avoid exposing critical IDs in API responses. Consider using role-based access to ensure only authorized users can access sensitive information.
Thorough Testing: Perform comprehensive security testing, particularly on features that involve user roles, permissions, and collaboration.
This vulnerability underscores the importance of robust access control in multi-user platforms. Even a simple oversight can lead to complete system compromise. Always think critically, test thoroughly, and secure your endpoints.
This vulnerability allowed us to escalate our privileges from a member to an admin, ultimately taking over an entire workspace. The issues we discovered stemmed from a lack of proper access control at the API level and exposed UUIDs that made exploitation straightforward.
