# CVE-2025-53967: Command injection in Figma MCP Server

> Unauthenticated remote attackers can execute arbitrary OS commands via crafted HTTP requests in the Figma MCP Server.

- **Severity:** High 8.0 (`CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Oct 2025
- **Updated:** 8 Oct 2025

## What is CVE-2025-53967?

CVE-2025-53967 is a high-severity command injection vulnerability in Framelink Figma MCP Server, published on 8 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Framelink Figma MCP Server before 0.6.3 allows an unauthenticated remote attacker to execute arbitrary operating system commands via a crafted HTTP POST request with shell metacharacters in input that is used by a fetchWithRetry curl command. The vulnerable endpoint fails to properly sanitize user-supplied input, enabling the attacker to inject malicious commands that are executed with the privileges of the MCP process. Exploitation requires network access to the MCP interface.

Weakness: CWE-420 (Unprotected Alternate Channel)

## Which versions are affected by CVE-2025-53967?


## How do I fix CVE-2025-53967?

Upgrade to a fixed version.

## Is CVE-2025-53967 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53967 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-53967 and fix it if it is affected.

What it is: CVE-2025-53967 is a high-severity command injection vulnerability in Framelink Figma MCP Server, published on 8 Oct 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-53967 exists.

Affected product: Framelink Figma MCP Server. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-53967/ (Markdown: https://insights.sbomify.com/CVE-2025-53967/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-53967
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-53967
- OSV: https://osv.dev/vulnerability/CVE-2025-53967

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-53967/
Summaries are generated and may contain mistakes; the official description above is the record.