A critical OS command injection vulnerability in the BurtTheCoder mcp-dnstwist tool allows unauthenticated remote attackers to achieve full host compromise.

The application utilizes the child_process.exec function to execute shell commands constructed from user-supplied input without proper sanitization or argument separation. An unauthenticated attacker can inject shell metacharacters through the nameservers parameter to execute arbitrary operating system commands with the privileges of the MCP server process.

Successful exploitation of this vulnerability permits an attacker to execute arbitrary commands on the underlying host, resulting in a total loss of confidentiality, integrity, and availability. Given the CVSS score of 7.3, this flaw poses a severe risk to any infrastructure hosting the mcp-dnstwist component, as it grants attackers the ability to exfiltrate sensitive data, modify system files, or disrupt critical services.

Immediate Action: There is currently no official patch available. Administrators should immediately restrict network access to the MCP interface to trusted internal networks only or disable the tool until a secure update is released.

Proactive Monitoring: Monitor system logs for unexpected child process execution spawned by the mcp-dnstwist process, particularly those involving shell metacharacters or unauthorized network connections.

Compensating Controls: Implement a Web Application Firewall (WAF) or an API gateway to inspect and filter incoming traffic to the MCP interface, blocking requests containing common shell injection patterns like semicolons, pipes, or redirection characters.

Public Exploit Available: Yes, a proof-of-concept exists as documented in the security researcher's write-up at the referenced GitHub repository.

Due to the availability of a public proof-of-concept and the high potential impact of remote code execution, this vulnerability requires urgent attention. Organizations currently utilizing mcp-dnstwist must isolate the affected server from untrusted networks immediately. Security teams should prioritize monitoring for the specific exploitation patterns described in the technical write-up and apply the vendor-provided update as soon as it becomes available.