liketrek TREK up to 3.0.x URL Validation placeService.ts server-side request forgery

Summaryinfo

A vulnerability marked as critical has been reported in liketrek TREK up to 3.0.x. This impacts the function importGoogleList/importNaverList/resolveGoogleMapsUrl of the file server/src/services/placeService.ts of the component URL Validation. This manipulation causes server-side request forgery. This vulnerability is registered as CVE-2026-54508. Remote exploitation of the attack is possible. No exploit is available.

Detailsinfo

A vulnerability classified as critical was found in liketrek TREK up to 3.0.x. Affected by this vulnerability is the function importGoogleList/importNaverList/resolveGoogleMapsUrl of the file server/src/services/placeService.ts of the component URL Validation. The manipulation with an unknown input leads to a server-side request forgery vulnerability. The CWE definition for the vulnerability is CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

The advisory is shared at github.com. This vulnerability is known as CVE-2026-54508 since 06/15/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available.

Upgrading to version 3.1.0 eliminates this vulnerability.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Vendor

• liketrek

Name

• TREK

Version

• 3.0

Website

• Product: https://github.com/liketrek/TREK/

CPE 2.3info

• 🔒

CPE 2.2info

• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion