Description

A vulnerability was identified in 03-lovepreetSingh MCP up to f95d035c5317fad81af9828286631053ccb23546. This issue affects the function create_file of the file app/api/mcp/route.ts. Such manipulation of the argument filePath/content leads to path traversal. The attack can be launched remotely. The exploit is publicly available and might be used. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. 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": "7.3",
  "pubDate": "2026-09-20T19:17:12.960Z",
  "pubdate": "2026-09-20T19:17:12.960Z",
  "executiveSummary": "A critical path traversal vulnerability exists in the 03-lovepreetSingh MCP project, specifically within the file creation logic. The vulnerability stems from improper neutralization of input arguments used for file system operations.\nBy manipulating the 'filePath' or 'content' parameters within the 'create_file' function of 'app/api/mcp/route.ts', a remote, unauthenticated attacker can escape the intended directory boundaries.\nThis allows for unauthorized file creation or overwriting of arbitrary files on the underlying host system. Given that the exploit is publicly available and the project remains unpatched, the risk of exploitation is high.\nThe vulnerability requires no authentication and can be triggered remotely, enabling attackers to gain persistence, modify application configuration, or potentially execute arbitrary code if sensitive system files or scripts are overwritten.\nThe affected codebase includes all versions up to commit f95d035c5317fad81af9828286631053ccb23546, and no official fix has been provided by the maintainers.",
  "technicalDetails": "The vulnerability is located in the 'create_file' function within 'app/api/mcp/route.ts'. The core issue is the lack of sufficient input sanitization and validation for the 'filePath' argument before it is passed to file system APIs.\nThe application fails to resolve or normalize the provided path, allowing for the inclusion of traversal sequences such as '../'. These sequences permit an attacker to escape the application's root directory and access or create files in restricted locations.\nAn attack flow commences when an attacker submits a crafted HTTP request to the vulnerable API endpoint. By injecting directory traversal characters into the 'filePath' parameter, the attacker forces the application to treat an absolute or relative path outside the target directory as the intended destination.\nBecause the 'create_file' function lacks an implementation of path containment checks (e.g., verifying that the resolved path starts with a permitted base directory), the underlying operating system executes the write operation at the attacker-specified location.\nThis exploit is executable remotely without requiring prior authentication. The impact is significant; an attacker can overwrite critical system binaries, configuration files, or inject malicious content into sensitive directories, facilitating remote code execution or complete system compromise.\nThe lack of input filtering for the 'content' parameter may also be leveraged in conjunction with path traversal to ensure that the malicious payload is precisely written to the target file. Since the exploit code is publicly documented, the barrier to entry for exploitation is low, necessitating immediate defensive action by operators of the affected software."
}