CyberRota Analysis
AI-GeneratedThe TREK collaborative travel planner prior to version 3.1.3 is vulnerable to improper validation of user-supplied identifiers in file upload and link actions, allowing authenticated users to access and disclose reservation details from other users' private trips. This could lead to unauthorized visibility of sensitive information, such as reservation titles, across trip boundaries. Organizations using affected versions should prioritize this vulnerability to protect user privacy and data integrity.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
TREK is a collaborative travel planner. Prior to 3.1.3, TREK file upload, update, and link actions accept attacker-controlled reservation_id, place_id, and assignment_id values without using findForeignLinkTarget() to verify that the referenced object belongs to the file's trip. An authenticated user with file-edit permission on any accessible trip can submit a foreign reservation identifier through POST /api/trips/:tripId/files/:id/link, POST /api/trips/:tripId/files, or PUT /api/trips/:tripId/files/:id. Subsequent reads through FILE_SELECT or getFileLinks() join the foreign reservation and return reservation_title, disclosing reservation existence and titles across private trip boundaries. This issue is fixed in version 3.1.3.