CyberRota Analysis
AI-GeneratedThe TREK collaborative travel planner prior to version 3.1.0 is vulnerable due to improper handling of user-supplied HTML in trip titles, which can lead to content spoofing and UI redress attacks when the Journey add-on is enabled. Although the impact is limited by the default Content Security Policy, trip owners should be aware that malicious HTML can still affect collaborators' sessions. Organizations using TREK should prioritize upgrading to version 3.1.0 to mitigate this risk.
Public Exploit Signal
A public exploit, PoC, GitHub repository or Metasploit reference was detected for this CVE.
Note: these links are listed for security research and verification purposes only.
Original NVD Description
TREK is a collaborative travel planner. Prior to 3.1.0, when the Journey add-on is enabled, TREK interpolates the unescaped activeSuggestion.title value into journey.frontpage.suggestionText through client/src/i18n/TranslationContext.tsx and renders the result with dangerouslySetInnerHTML in client/src/pages/JourneyPage.tsx. A trip owner can store HTML in a qualifying trip title, and GET /api/journeys/suggestions returns that title through getSuggestions(userId) to a collaborator who opens the authenticated Journey page. The markup is inserted as live DOM in the collaborator's session, enabling content spoofing and UI redress, although the default Content Security Policy blocks inline handlers and script execution. This issue is fixed in version 3.1.0.