CVE-2026-54509 TREK IDOR: any authenticated user can read another user's journey share token (full journey leak)
Authenticated users can access other users' journey share tokens, leading to unauthorized disclosure of private travel data.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-54509?
CVE-2026-54509 is a medium-severity missing authorization vulnerability in mauriceboe TREK, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
TREK is a collaborative travel planner. From 3.0.0 until 3.1.0, the GET /api/journeys/:id/share-link route in server/src/routes/journey.ts returns the result of getJourneyShareLink() from server/src/services/journeyShareService.ts without checking whether the authenticated requester can access the journey. Any ordinary authenticated user can enumerate sequential journey IDs and retrieve tokens from journey_share_tokens for another user's journey. The token grants unauthenticated access through GET /api/public/journey/:token to the shared journey's entries, captions, locations, moods, gallery photos, photo paths, and asset identifiers. This issue is fixed in version 3.1.0.
Weakness: CWE-862
Which versions are affected by CVE-2026-54509?
How do I fix CVE-2026-54509?
No fix has been published for CVE-2026-54509 yet. Limit exposure of the affected software until one is available.
Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.
Is CVE-2026-54509 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54509 exists.
Sources
Also known as GHSA-mx6m-qxv8-w624.