CVE-2026-62945 TREK: Cross-trip reservation title disclosure via file links

Medium 4.3 Published Updated

Authenticated users can leak private reservation titles from other trips by manipulating file link identifiers, exposing sensitive travel data.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-62945?

CVE-2026-62945 is a medium-severity missing authorization vulnerability in mauriceboe TREK, published on 20 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

TREK is a collaborative travel planner. Prior to 3.1.3, TREK file upload, update, and link actions accept attacker-controlled reservation_id, place_id, and assignment_id values without using findForeignLinkTarget() to verify that the referenced object belongs to the file's trip. An authenticated user with file-edit permission on any accessible trip can submit a foreign reservation identifier through POST /api/trips/:tripId/files/:id/link, POST /api/trips/:tripId/files, or PUT /api/trips/:tripId/files/:id. Subsequent reads through FILE_SELECT or getFileLinks() join the foreign reservation and return reservation_title, disclosing reservation existence and titles across private trip boundaries. This issue is fixed in version 3.1.3.

Weakness: CWE-639

Which versions are affected by CVE-2026-62945?

How do I fix CVE-2026-62945?

No fix has been published for CVE-2026-62945 yet. Limit exposure of the affected software until one is available.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-62945 being exploited?

There is no known exploitation of CVE-2026-62945 in the wild and no public exploit code.

Sources

Also known as GHSA-r4cp-666p-8f69.

Is CVE-2026-62945 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free