CVE-2025-15061
Command Injection in Framelink Figma MCP Server Allows RCE
Publication date: 2026-01-23
Last updated on: 2026-01-23
Assigner: Zero Day Initiative
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| framelink | figma_mcp_server | to 0.6.3 (exc) |
| unknown_vendor | figma_developer_mcp | to 0.6.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-78 | The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-15061 is a critical command injection vulnerability in the Framelink Figma MCP Server, specifically in the fetchWithRetry method. The vulnerability occurs because the server improperly validates user-supplied input before using it in system calls, allowing remote attackers to inject and execute arbitrary commands on the server without authentication. This happens due to unsafe use of Node.js's child_process.exec function with unvalidated input, enabling shell metacharacter injection. [1, 2]
How can this vulnerability impact me? :
This vulnerability allows remote attackers to execute arbitrary code on the affected server with the privileges of the service account running the MCP Server. Exploitation can lead to full compromise of the server, including unauthorized access, data manipulation, and disruption of services, impacting confidentiality, integrity, and availability of the system. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can involve testing the vulnerable parameters for command injection by injecting payloads that execute harmless commands and checking for their effects. For example, injecting payloads like `$(id > /tmp/TEST1)` into parameters such as "fileKey" can help verify if arbitrary commands are executed by checking the presence and content of the /tmp/TEST1 file. Network monitoring for unusual command execution patterns or unexpected outbound connections from the MCP Server process may also help detect exploitation attempts. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include updating the figma-developer-mcp package to version 0.6.3 or later, which includes input validation and output sanitization to prevent command injection. Alternatively, replacing the use of child_process.exec with child_process.execFile in the server code can prevent shell interpretation of user inputs. Implementing strict input validation and sanitization on all user-supplied parameters before they are used in system calls is also recommended. Additionally, restricting network access to the MCP Server and monitoring for suspicious activity can help reduce risk until patches are applied. [1, 2]
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The provided resources do not explicitly discuss the impact of this vulnerability on compliance with common standards and regulations such as GDPR or HIPAA. However, since the vulnerability allows remote code execution without authentication and can compromise confidentiality, integrity, and availability of the affected system, it could potentially lead to violations of such regulations if sensitive data is exposed or systems are disrupted. No direct compliance impact details are given. [1, 2]