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.
Published: 2026-08-20
Score: 6.5 Medium
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The vulnerability resides in an authenticated endpoint that returns a share link for a journey without verifying the requester's authorization to access that journey.An attacker who is logged in can simply enumerate sequential journey identifiers, retrieve the associated share token, and then use an unauthenticated public endpoint to view all data tied to that journey, including entries, captions, locations, moods, gallery photos, photo paths, and asset identifiers. This flaw is a classic missing authorization (CWE‑862) that results in sensitive data exposure.

Affected Systems

The affected product is TREK, a collaborative travel planner, published under the vendor mauriceboe. The flaw exists in versions from 3.0.0 up through, but not including, 3.1.0. Version 3.1.0 and later contain the fix.

Risk and Exploitability

With a CVSS score of 6.5 the vulnerability is moderate in severity. No EPSS score is provided, and the vulnerability is not listed in CISA’s KEV catalog. The likely attack vector requires an attacker to be authenticated to the application, after which they can brute‑force or systematically request journey IDs, obtain the share token, and then access full journey data via a public API. Given the lack of immediate exploitation scores, the risk remains present until the authorized check is restored or the software is updated.

Generated by OpenCVE AI on August 21, 2026 at 00:25 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Upgrade TREK to version 3.1.0 or later, where the share link route now validates user permissions.
  • If an upgrade is delayed, temporarily disable the /api/journeys/:id/share-link endpoint for authenticated users or add a custom authorization filter that denies requests without proper ownership.
  • Review all journey‑related endpoints to ensure they enforce authentication and authorization checks before returning data, and monitor logs for anomalous enumeration attempts.

Generated by OpenCVE AI on August 21, 2026 at 00:25 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sun, 23 Aug 2026 04:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'poc', 'Technical Impact': 'partial'}, 'version': '2.0.3'}


Fri, 21 Aug 2026 00:45:00 +0000

Type Values Removed Values Added
First Time appeared Mauriceboe
Mauriceboe trek
Vendors & Products Mauriceboe
Mauriceboe trek

Thu, 20 Aug 2026 22:00:00 +0000

Type Values Removed Values Added
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.
Title TREK IDOR: any authenticated user can read another user's journey share token (full journey leak)
Weaknesses CWE-862
References
Metrics cvssV3_1

{'score': 6.5, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-08-21T14:57:42.795Z

Reserved: 2026-06-15T18:01:15.513Z

Link: CVE-2026-54509

cve-icon Vulnrichment

Updated: 2026-08-21T14:56:53.431Z

cve-icon NVD

Status : Received

Published: 2026-08-20T22:17:21.553

Modified: 2026-08-21T15:16:41.753

Link: CVE-2026-54509

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-21T00:30:07Z

Weaknesses