CVE-2026-54509Public exploitNetwork attack vector

Journey disclosure via missing share-link authorization

Published Aug 20, 2026 · Updated Aug 20, 2026

Missing authorization in the Journey addon in Maurice Boe TREK before 3.1.0 allows remote authenticated users to read other users' shared journey data. The GET /api/journeys/:id/share-link route in server/src/routes/journey.ts returns getJourneyShareLink() results from server/src/services/journeyShareService.ts without verifying that the requester can access the journey, so sequential journey IDs expose share tokens from journey_share_tokens. Any ordinary account can enumerate IDs, harvest tokens for journeys another user has shared, and then use GET /api/public/journey/:token without authentication to read entries, captions, locations, moods, gallery photos, photo paths, and asset identifiers.

CVSS severity6.5
Medium
EPSS probability0.30%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Missing authorization in the Journey addon in Maurice Boe TREK before 3.1.0 allows remote authenticated users to read other users' shared journey data. The GET /api/journeys/:id/share-link route in server/src/routes/journey.ts returns getJourneyShareLink() results from server/src/services/journeyShareService.ts without verifying that the requester can access the journey, so sequential journey IDs expose share tokens from journey_share_tokens. Any ordinary account can enumerate IDs, harvest tokens for journeys another user has shared, and then use GET /api/public/journey/:token without authentication to read entries, captions, locations, moods, gallery photos, photo paths, and asset identifiers.

The record

CVE
CVE-2026-54509
Published
Aug 20, 2026
Updated
Aug 20, 2026
Vendor
Maurice Boe
Product
TREK
Classifications
CWE-862, T1213
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Aug 20, 2026CVE publishedPublication date reported by the CVE source.
  2. Aug 20, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=>= 3.0.0, < 3.1.0

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Maurice Boe · TREKversion=>= 3.0.0, < 3.1.0

Published CVSS scores

6.5GitHubCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-862Missing Authorization
T1213Data from Information Repositories

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo