Description

A security flaw has been discovered in Hulupeep mcp-ui-probe up to 0.2.0. Affected is the function get_journey/delete_journey/analyze_journey/usage_stats of the file src/journey/JourneyStorage.ts of the component Journey/Usage. The manipulation of the argument journeyId/filename results in path traversal. The attack requires a local approach. The project was informed of the problem early through an issue report but has not responded yet.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "5.3",
  "pubDate": "2026-08-08T08:16:51.837Z",
  "pubdate": "2026-08-08T08:16:51.837Z",
  "executiveSummary": "A path traversal vulnerability has been identified in the Hulupeep mcp-ui-probe component, specifically within the Journey/Usage module affecting versions up to 0.2.0. The security flaw stems from the improper handling of user-supplied input passed to file and journey identifiers. The vulnerability affects the functions get_journey, delete_journey, analyze_journey, and usage_stats located within the source file src/journey/JourneyStorage.ts.\nSuccessful exploitation of this vulnerability allows local attackers to manipulate the journeyId or filename arguments to traverse the directory structure and access, analyze, or delete arbitrary files outside the intended storage directory, depending on the privileges of the executing process.\nThe risk implication is rated as significant due to potential unauthorized file system access and manipulation. The attack vector is local, requiring the threat actor to have local execution capabilities or a mechanism to supply malicious input to the vulnerable functions. The project was informed of the problem through an issue report but has not provided a vendor response or patch at this time.",
  "technicalDetails": "The vulnerability is rooted in the JourneyStorage component of the mcp-ui-probe project, specifically inside the src/journey/JourneyStorage.ts file. The functions get_journey, delete_journey, analyze_journey, and usage_stats accept arguments such as journeyId and filename without performing adequate input sanitization, normalization, or validation.\nWhen an attacker supplies crafted strings containing directory traversal sequences, such as dot-dot-slash sequences (e.g., ../), the underlying file system operations interpret these sequences relative to the working directory. Consequently, file paths are resolved outside the intended journey storage boundary, allowing access to unauthorized system resources.\nThe attack flow proceeds as follows: First, the local attacker identifies an interface or execution context that invokes one of the vulnerable functions: get_journey, delete_journey, analyze_journey, or usage_stats. Second, the attacker crafts a malicious payload incorporating path traversal patterns within the journeyId or filename parameters. Third, the application passes this unsanitized input directly into file system APIs within src/journey/JourneyStorage.ts. Finally, the operating system resolves the path, granting the attacker the ability to read, analyze, or delete target files based on the file system permissions of the application process.\nThe affected versions include Hulupeep mcp-ui-probe up to version 0.2.0. The vulnerability requires a local approach for execution, and exploitation does not inherently require network exposure, relying instead on local access vectors or interfaces exposed by the application."
}