Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2026-54509— TREK IDOR: any authenticated user can read another user's journey share token (full journey leak)

Quick assessment

Affected
mauriceboe TREK
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

TREK 是一款协作式旅行规划应用。在版本 3.0.0 至 3.1.0 之间， 中的 路由直接返回了 中 的结果，而未验证经身份认证的用户是否有权访问该旅程。任何普通已认证用户都可以通过枚举连续的旅程 ID，获取其他用户旅程的 中的令牌。该令牌允许通过 接口以未认证方式访问共享旅程的条目、字幕、地点、情绪标签、相册照片、照片路径及资产标识符。此问题已在版本 3.1.0 中得到修复。

CVSS 6.5 · Medium EPSS 0.30% · P23

Possible ATT&CK Techniques 1 AI

T1552 · Unsecured Credentials

Affected Version Matrix 1

VendorProduct Version RangeStatus
mauriceboe TREK >= 3.0.0, < 3.1.0 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-54509

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
TREK IDOR: any authenticated user can read another user's journey share token (full journey leak)
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
授权机制缺失
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
mauriceboe TREK >= 3.0.0, < 3.1.0 -

II. Public POCs for CVE-2026-54509

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-54509

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-54509 (1)

Vendor Advisories for CVE-2026-54509 (1)

Other References for CVE-2026-54509 (1)

Same Patch Batch · mauriceboe · 2026-08-20 · 4 CVEs total

CVE-2026-54508 5.3 MEDIUM TREK: Blind SSRF via unvalidated redirect-following in Google/Naver list import and Maps U
CVE-2026-62945 4.3 MEDIUM TREK: Cross-trip reservation title disclosure via file links
CVE-2026-54505 2.0 LOW TREK: Stored cross-user HTML injection via trip title in the Journey suggestion banner

IV. Related Vulnerabilities

Same product: TREK
Same vendor: mauriceboe
Same weakness: CWE-862

V. Comments for CVE-2026-54509

No comments yet

Leave a comment