An unauthenticated remote attacker can exploit SSRF and path traversal vulnerabilities in Algovate xhs-mcp 0.8.11 to access internal network services and sensitive local filesystem data.

The application fails to validate user-supplied input in the xhs_publish_content function, leading to Server-Side Request Forgery (CWE-918) and Path Traversal (CWE-22). An unauthenticated attacker can manipulate the media_paths argument to trigger unauthorized outbound HTTP requests or access arbitrary files on the host system.

Successful exploitation allows an attacker to bypass network perimeters by using the server as a proxy to scan internal services, potentially exposing non-public APIs or metadata services. Furthermore, the path traversal vulnerability enables unauthorized read access to the underlying server filesystem, which may result in the exposure of configuration files, credentials, or sensitive application data. Given the CVSS score of 7.3, this vulnerability poses a significant risk to the confidentiality and integrity of the affected environment.

Immediate Action: As no official patch is currently available, restrict access to the MCP interface to trusted users only and implement strict network egress filtering to prevent the server from reaching internal network segments.

Proactive Monitoring: Review application and system logs for unusual outbound connection attempts from the server and monitor for directory traversal patterns (e.g., ../) in requests directed at the xhs_publish_content endpoint.

Compensating Controls: Deploy a Web Application Firewall (WAF) or an API gateway with request validation rules to block input containing directory traversal sequences and to restrict outbound requests to a predefined allowlist of trusted domains.

Public Exploit Available: Yes, a proof-of-concept is documented in the security researcher's report at GitHub (https://github.com/BruceJqs/public_exp/issues/21).

Given the availability of a public proof-of-concept and the lack of a vendor-supplied patch, organizations utilizing Algovate xhs-mcp should treat this vulnerability with high priority. We recommend isolating the affected service from production networks and implementing the suggested compensating controls until a formal update is released by the vendor.