figma-developer-mcp vulnerable to command injection in get_figma_data tool
CVE-2025-53967 · GHSA-gxw4-4fc5-9gr5 · published 2025-09-30
- Severity
- High
- CVSS score
- 7.5
- Chance of exploitation (EPSS)
- 7.6%
- Fixed in
- 0.6.3
- Exploitation Public proof of concept
- Automatable No
- Technical impact Partial
- CISA SSVC
Command Injection / Remote Code Execution (RCE)
Upgrade figma-developer-mcp to 0.6.3 or later. If you start it from an MCP config with npx or uvx, pin that version so an old cached copy is not used.
To mitigate this vulnerability, I suggest to avoid using childprocess.exec with untrusted input. Instead, use a safer API such as childprocess.execFile, which allows you to pass arguments as a separate array — avoiding shell interpretation entirely. NOTE: This mitigation—and others like input validation—have been implemented in versions 0.6.3 and above. To fix the issue, make sure you're using a version >=0.6.3.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| figma-developer-mcp | npm | <= 0.6.2 | 0.6.3 |
- CriticalUnauthenticated Remote Code Execution in Langflow via Public Flow Build EndpointlangflowExploited
- CriticalRay is vulnerable to Critical RCE via Safari & Firefox Browsers through DNS Rebinding AttackrayExploited
- CriticalLangflow Unauth RCElangflow, langflow-baseExploited
- HighLiteLLM: Authenticated command execution via MCP stdio test endpointslitellmExploited
- CriticalMLflow vulnerable to remote code execution on unauthenticated servers via third-party scorer deserialization importing caller-placed artifacmlflow
- CriticalAgno: Arbitrary code execution via `eval()` on `field_type` in `FunctionCall`agno
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.