Description

potpie through 2.0.0 fails to verify user ownership on the POST /conversations/{conversation_id}/code-changes/sync endpoint. Authenticated attackers can write arbitrary file changes into other users' conversations by supplying their conversation IDs, allowing unauthorized modification of pending changes.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "6.5",
  "pubDate": "2026-09-04T15:17:44.847Z",
  "pubdate": "2026-09-04T15:17:44.847Z",
  "executiveSummary": "The potpie application, in versions through 2.0.0, contains an Insecure Direct Object Reference (IDOR) vulnerability within the synchronization mechanism for code changes. This flaw originates from a failure to validate user ownership of a conversation resource when processing requests to the POST /conversations/{conversation_id}/code-changes/sync endpoint.\nThe vulnerability allows an authenticated attacker to perform unauthorized write operations on arbitrary conversations by manipulating the 'conversation_id' parameter. By successfully exploiting this, an attacker can modify pending code changes belonging to any other user within the system.\nThe impact is significant, as it enables unauthorized data modification and potential integrity compromise of user-generated content. Successful exploitation requires an active authenticated session, but does not necessitate elevated administrative privileges, as the system fails to enforce ownership checks at the application logic layer. This poses a severe risk to data integrity and collaborative security, as attackers can inject malicious or disruptive code changes into workflows that they do not own.",
  "technicalDetails": "The vulnerability resides in the backend request handling logic for the /conversations/{conversation_id}/code-changes/sync endpoint. The root cause is a lack of server-side authorization checks that verify whether the currently authenticated user is authorized to modify the conversation identified by the 'conversation_id' path parameter.\nIn a secure implementation, the application must perform an explicit authorization check comparing the authenticated user's session identifier against the owner ID associated with the specified 'conversation_id' in the underlying database. In the affected versions of potpie, the backend controller proceeds to process the payload and execute file-system write operations based solely on the user's authenticated status, disregarding whether the user has legitimate access to the target resource.\nThe attack flow proceeds as follows: First, the attacker initiates an authenticated session to the potpie instance. Second, the attacker identifies a target 'conversation_id' belonging to another user. This is often achieved through predictable resource identification or by observing existing synchronization traffic. Third, the attacker constructs a POST request to the target endpoint, inserting the illicit 'conversation_id' into the URL path and providing a payload containing arbitrary code changes. Because the application logic fails to validate the user's relationship to the conversation, it accepts the request and proceeds to apply these changes to the target conversation.\nThe component responsible for this flaw is the request-processing logic within the conversation synchronization module. Because the endpoint processes these changes by writing to the storage layer associated with the provided ID, the attacker can effectively overwrite or append pending changes without the knowledge of the legitimate owner. This vulnerability is accessible over the network to any authenticated user, requiring no additional privileges beyond a standard account. The post-exploitation impact includes the potential for code injection into legitimate development workflows, corruption of collaborative sessions, and the circumvention of access control policies intended to isolate conversation data between users."
}