Part 77 · Module 11: Capstone

Incident: A fallback path that handed URLs to a shell

7 min read·13 Oct 2026

Module 11 · Incident file · About 30 minutes

What happened

Twelve weeks from first contact to complete fix, with the details public after two (red) and a partial fix between (amber); dates from Imperva and the advisory.

The Framelink Figma MCP server, published on npm as figma-developer-mcp, gives coding assistants such as Cursor the contents of Figma designs. Imperva describes it as launched in February 2025, with more than 10,000 GitHub stars and over 100,000 downloads a month (Imperva, 7 October 2025). On 29 September 2025 the maintainers published advisory GHSA-gxw4-4fc5-9gr5, CVE-2025-53967: "A command injection vulnerability exists in the figma-developer-mcp MCP Server", rated High, CVSS 7.5, affecting every version up to 0.6.2 and fixed in 0.6.3 (GitHub Advisory Database). The National Vulnerability Database scores it 8.0; the sources differ.

The Hacker News reported it on 8 October 2025 from Imperva's research by Yohann Sillam (Lakshmanan, The Hacker News). The advisory states the cost: "Successful exploitation can lead to remote code execution under the server process's privileges." Imperva's timeline runs from first contact on 8 July 2025, through a public pull request that exposed the details on 22 July and a partial fix on 13 August, to the complete fix on 29 September. The advisory credits a reporter named dellalibera; Imperva describes its own report. Both are recorded here as each source states them.

What happened

The rest of this course is yours to keep