Vulnerability 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.
CVSS Score
MEDIUM
Related Weaknesses (CWE)
References
- https://github.com/liketrek/TREK/commit/03cdb4d27689922460ba87085d04b426d4d40d26
- https://github.com/liketrek/TREK/pull/1324
- https://github.com/liketrek/TREK/releases/tag/v3.1.3
- https://github.com/liketrek/TREK/security/advisories/GHSA-r4cp-666p-8f69
FAQ
What is CVE-2026-62945?
CVE-2026-62945 is a vulnerability with a CVSS score of 4.3 (MEDIUM). 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 findForei...
How severe is CVE-2026-62945?
CVE-2026-62945 has been rated MEDIUM with a CVSS base score of 4.3/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-62945?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.