MCP-Server

The server has critical security risks related to file system interaction. The MCP Tools (`read_file`, `write_file`, `list_directory`, `search_files`) and File Management API endpoints (`/files/{file_path:path}`) directly use user-provided paths without sufficient validation against directory traversal attacks (e.g., `../`). This could allow unauthorized access, modification, or deletion of arbitrary files outside intended data directories. Additionally, default admin credentials (`Jatin23K`, `#JK2025sy#`) are hardcoded in `backend/data/users/users.json`, which is a common vulnerability if not changed. The broad CORS policy (`Access-Control-Allow-Origin: *`) configured for development in `firebase.json` and potentially in `main.py` poses a risk if not restricted for production APIs. While some security measures like JWT authentication, bcrypt, rate limiting, and input sanitization methods are present in `security_manager.py`, their application is not consistently demonstrated or robust enough to mitigate direct file system access vulnerabilities.