| Title | mauriceboe TREK <= 3.0.22 SQL Injection |
|---|
| Description | SQL injection via unvalidated column names in journey entry update in TREK <= 3.0.22. The journeyService.updateEntry function constructs SQL UPDATE statements by directly incorporating request body keys without validating against an allowlist. While values are parameterized, column names are not. An authenticated low-privilege user with journey editing permissions can exploit this by submitting malicious JSON keys (e.g., "story = (SELECT password_hash FROM users WHERE role='admin'), updated_at") to extract sensitive data including emails, password hashes, and MFA secrets, and perform mass-assignment attacks on protected columns. Enables full database read access and potential account takeover via offline hash cracking. CVSS 8.5 (AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N). CWE-89. Fixed in 3.1.0. |
|---|
| Source | ⚠️ https://github.com/mauriceboe/TREK/security/advisories/GHSA-627x-pmfq-98qv |
|---|
| User | ByteJMP (UID 99294) |
|---|
| Submission | 07/12/2026 06:38 (1 month ago) |
|---|
| Moderation | 08/25/2026 08:01 (1 month later) |
|---|
| Status | Accepted |
|---|
| VulDB entry | 394940 [liketrek TREK up to 3.0.22 Journey Entry Update journey.controller.t journeyService.updateEntry sql injection] |
|---|
| Points | 20 |
|---|