CVE-2026-45410: fallo de gravedad media en mauriceboe TREK
Time-based user enumeration in TREK authentication endpoint
Publicada el · Actualizada el
Aviso por correo cuando entre en el KEV, tenga PoC pública o suba de nota.
13Vexday Risk Score
Sin señal de explotación. Ningún artefacto público de explotación conocido hasta ahora.
ssvc Trackcvss 5.3epss 0.2%
TREK is a collaborative travel planner. Prior to 3.0.18, early return on missing user during login flow allowed an attacker to enumerate valid user accounts via response timing discrepancy. When an email address existed in the database, the backend performed a bcrypt password comparison before returning a 401 Unauthorized, adding ~370 ms of latency. When the email did not exist, the backend returned immediately (~10 ms). This ~14× timing difference could be detected without any difference in HTTP status codes or response bodies. This vulnerability is fixed in 3.0.18.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Productos afectados
mauriceboe · TREKCVEs relacionadas — mauriceboe TREK
En el mismo producto, de las más peligrosas a las menos.
CVE-2026-54505LOWTREK: Stored cross-user HTML injection via trip title in the Journey suggestion bannerEPSS 0.6%CVE-2026-54508MEDIUMTREK: Blind SSRF via unvalidated redirect-following in Google/Naver list import and Maps URL resolutionEPSS 0.4%CVE-2026-54509MEDIUMTREK IDOR: any authenticated user can read another user's journey share token (full journey leak)EPSS 0.4%CVE-2026-77293HIGHTREK: Cross-user note-file deletion (IDOR / Broken Access Control)EPSS 0.4%CVE-2026-62945MEDIUMTREK: Cross-trip reservation title disclosure via file linksEPSS 0.3%CVE-2026-77294HIGHTREK: Server-Side Request Forgery via User-Configurable LLM Base URLEPSS 0.3%