CVE-2026-54505: mauriceboe TREK · Cross-site Scripting
Affects mauriceboe TREKSource CVE Database V5
Not known to be exploited · CVSS 2.0 Low : upgrade to 3.1.0 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.1.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:A/VC:N/VI:L/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 20 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Upgrade TREK and liketrek/TREK to 3.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| mauriceboeTREK | Affected
| Fixed in
|
GitHubliketrek/TREKpkg:github/liketrek/TREKOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade TREK to version 3.1.0 or later, where this vulnerability is fixed. No additional mitigation is required as the fix addresses the root cause by properly escaping or sanitizing user input before rendering.
Description
CVE-2026-54505 is a cross-site scripting (XSS) vulnerability in the TREK collaborative travel planner prior to version 3.1.0. When the Journey add-on is enabled, unescaped user input from trip titles is rendered directly into the DOM using dangerouslySetInnerHTML, allowing a trip owner to inject HTML that is then displayed to collaborators. Although the default Content Security Policy mitigates script execution, this flaw can enable content spoofing and UI redress attacks. The issue is fixed in version 3.1.0.