TREK: Blind SSRF via unvalidated redirect-following in Google/Naver list import and Maps URL resolution
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- None
- Impact type
- —
- Confidentiality · integrity · availability
- Low · Low · Low
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA.
Summary
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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| mauriceboe | TREK | before 3.1.0 | 3.1.0 | Patch available | CNA |
- TREK Vendormauriceboe Affected before 3.1.0 Fixed in 3.1.0 Patch available CNA
Remediation
- Fix · CNA TREK (mauriceboe) Fixed in 3.1.0
Timeline
- 2026-10-02 Threatist record created from CVE-2026-54508
References
More mauriceboe vulnerabilities
- TI-2026-53961 TREK: Server-Side Request Forgery via User-Configurable LLM Base URL CVSS 3.1HIGH 8.1
- TI-2026-53960 TREK: Cross-user note-file deletion (IDOR / Broken Access Control) CVSS 3.1HIGH 7.1
- TI-2026-53966 Information disclosure in mauriceboe TREK CVSS 3.1MEDIUM 5.3
- TI-2026-33199 Time-based user enumeration in TREK authentication endpoint CVSS 3.1MEDIUM 5.3
- TI-2026-39355 TREK IDOR: any authenticated user can read another user's journey share token (full journey leak) CVSS 3.1MEDIUM 6.5
- TI-2026-39351 TREK: Stored cross-user HTML injection via trip title in the Journey suggestion banner CVSS 4.0LOW 2.0
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences