Mauriceboe TREK
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- < 3.3.0
Fixed in 3.3.0
Mitigation
Upgrade TREK to 3.3.0 or later.
References
- Vendor advisory github.com/liketrek/TREK/security/advisories/G…
- Patch github.com/liketrek/TREK/pull/1520
- Patch github.com/liketrek/TREK/commit/19064b39176660…
1 more
- Release notes github.com/liketrek/TREK/releases/tag/v3.3.0
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.