Vulnerability in Framelink Figma MCP Server (CVE-2025-53967)
Summary
Vulnerability in Framelink Figma MCP Server (CVE-2025-53967). Confidential information can be exposed externally.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2025-53967 has been found in Framelink Figma MCP Server.
Confidential information can be exposed externally. CVSS score: 8.0/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Framelink Figma MCP Server CVE-2025-53967" on the vendor's site.
CVE-2025-53967 (Framelink Figma MCP Server) — CWE-420 / CVSS v3 8.0
Attack vector: adjacent-network / unauthenticated / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-420) exists in Framelink Figma MCP Server.
Check the vendor advisory for the affected versions of Framelink Figma MCP Server.
Severity: High (CVSS 8.0/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Framelink Figma MCP Server を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
References
- web cve@mitre.org
- web cve@mitre.org
- web cve@mitre.org