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

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

CVE-2026-54508— TREK: Blind SSRF via unvalidated redirect-following in Google/Naver list import and Maps URL resolution

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.1.0 版本之前，TREK 在 文件中的 和 函数，以及 文件中的 函数中，仅在原生重定向发生前对初始 URL 进行验证。受影响的这些函数会调用 中的 函数，但随后却使用带有 选项的 方法，而非采用通过 DNS 固定（DNS-pinned）机制的安全 路径。因此，攻击者可以通过控制的公开 URL 引导服务器重定向到回环地址（loopback）、RFC 1918 私有网络地址或云元数据地址，且不会在重定向过程中重新进行验证。 已认证为行程成员的用户可以通过列表导入相关路由发

CVSS 5.3 · Medium EPSS 0.31% · P24

Affected Version Matrix 1

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

I. Basic Information for CVE-2026-54508

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: Blind SSRF via unvalidated redirect-following in Google/Naver list import and Maps URL resolution
Source: CVE Program / CVE List V5
Vulnerability Description
TREK is a collaborative travel planner. Prior to 3.1.0, TREK validates only the initial URL before native redirect following in importGoogleList() and importNaverList() in server/src/services/placeService.ts and resolveGoogleMapsUrl() in server/src/services/mapsService.ts. The affected sinks call checkSsrf() from server/src/utils/ssrfGuard.ts and then use fetch() with redirect: 'follow' instead of the DNS-pinned safeFetch() path, so a public attacker-controlled URL can redirect the server to loopback, RFC 1918, or cloud metadata addresses without revalidation. An authenticated trip member can reach the list-import routes, and any authenticated user can reach /api/maps/resolve-url, allowing blind GET requests to internal services without response-body reflection. This issue is fixed in version 3.1.0.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N
Source: CVE Program / CVE List V5
Vulnerability Type
服务端请求伪造(SSRF)
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
mauriceboe TREK < 3.1.0 -

II. Public POCs for CVE-2026-54508

# 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-54508

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

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

Vendor Advisories for CVE-2026-54508 (1)

Other References for CVE-2026-54508 (1)

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

CVE-2026-54509 6.5 MEDIUM TREK IDOR: any authenticated user can read another user's journey share token (full journe
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-918

V. Comments for CVE-2026-54508

No comments yet

Leave a comment