CVE-2026-77293: TREK: Cross-user note-file deletion (IDOR / Broken Access Control)
TREK is a collaborative travel planner. Prior to 3.3.0, the DELETE /api/trips/:tripId/collab/notes/:noteId/files/:fileId endpoint authorizes an authenticated user against the attacker-controlled tripId but deleteNoteFile in server/src/services/collabService.ts resolves the target only by note and file identifiers without requiring the file to belong to that trip. A user with edit access to any trip can submit identifiers belonging to another user's trip and permanently delete that note-file attachment. Sequential identifiers make broad targeting practical, while attachment read operations remain trip-scoped and are not affected. This issue is fixed in version 3.3.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
TREKto a version that resolves this vulnerability.Fixed in 3.3.0
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated user who has edit access to any trip can exploit it. The attacker does not need access to the victim's trip, but needs note and file identifiers for an attachment in that trip.
What data or operations are affected?
The issue permits permanent deletion of note-file attachments belonging to another user's trip. Attachment read operations remain trip-scoped and are not affected.
Are installations running version 3.3.0 affected?
No. The issue affects TREK versions prior to 3.3.0 and is fixed in version 3.3.0.
How can I assess whether an instance may be vulnerable?
Instances running a version earlier than 3.3.0 may be vulnerable, particularly where users can receive edit access to trips. The vulnerable behavior is the delete endpoint accepting a trip identifier the requester may edit while resolving the target attachment solely from note and file identifiers.