CVE-2026-78864
Received Received - Intake

SQL Injection in Liketrek TREK Application

Publication date: 2026-08-25

Last updated on: 2026-08-25

Assigner: VulDB

Description
A vulnerability was determined in liketrek TREK up to 3.0.22. The affected element is the function journeyService.updateEntry of the file server/src/nest/journey/journey.controller.t of the component Journey Entry Update. This manipulation causes sql injection. It is possible to initiate the attack remotely. Upgrading to version 3.1.0 is sufficient to fix this issue. It is recommended to upgrade the affected component.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-25
Last Modified
2026-08-25
Generated
2026-08-25
AI Q&A
2026-08-25
EPSS Evaluated
N/A
NVD
CVE-2026-78864
EUVD
EUVD-2026-65458

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
liketrek trek to 3.0.22 (inc)
liketrek trek to 3.1.0 (exc)
liketrek trek 3.1.0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-74 The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-78864 is a SQL injection vulnerability in the TREK npm package versions up to 3.0.22. It exists in the journeyService.updateEntry function which constructs an SQL UPDATE statement using unvalidated keys from request body input. This allows attackers to inject malicious SQL commands by submitting specially crafted JSON keys.

Detection Guidance

To detect this SQL injection vulnerability, inspect network traffic for requests to the PATCH /api/journeys/entries/:id endpoint with raw JSON payloads containing suspicious keys like 'story', 'updated_at', or other unvalidated column names. Check server logs for malformed SQL queries or errors indicating improper neutralization of special elements.

Impact Analysis

This vulnerability allows low-privilege authenticated users to perform full database reads and unauthorized actions. Attackers can extract sensitive data like emails, bcrypt hashes, and encrypted MFA secrets. They can also modify protected columns leading to privacy bypasses and potential account impersonation. Offline cracking of extracted hashes could result in full account takeover.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive personal data, violating GDPR's data protection requirements and HIPAA's safeguards for protected health information. The ability to extract and potentially crack password hashes represents a significant data breach risk.

Mitigation Strategies

Immediately upgrade the TREK package to version 3.1.0 or later. Implement strict input validation for the journeyService.updateEntry function by using a column allow-list. Review database access logs for signs of exploitation and restrict low-privilege user permissions to limit potential damage.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-78864. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart