# CVE-2025-56803: Command injection in n/a

> A local attacker can execute arbitrary OS commands via a crafted plugin manifest in Figma Desktop for Windows, though the vendor disputes severity due to local-only scope.

- **Severity:** High 8.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Sep 2025
- **Updated:** 8 Sep 2025
- **Also known as:** GHSA-jj2f-fq9g-62qj

## What is CVE-2025-56803?

CVE-2025-56803 is a high-severity command injection vulnerability in n/a, published on 3 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Figma Desktop for Windows version 125.6.5 contains a command injection vulnerability in the local plugin loader. An attacker can execute arbitrary OS commands by setting a crafted build field in the plugin's manifest.json. This field is passed to child_process.exec without validation, leading to possible RCE. NOTE: this is disputed by the Supplier because the behavior only allows a local user to attack himself via a local plugin. The local build procedure, which is essential to the attack, is not executed for plugins shared to the Figma Community.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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

It affects 1 product.


Products: Figma Desktop.

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

No fix has been published for CVE-2025-56803 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-56803 being exploited?

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

Public exploit code:

- OS Command Injection Vulnerability via Plugin Execution in Figma Desktop Application (github_poc): https://github.com/yosasasutsut/CVE-2025-56803

## Fix prompt for AI coding agents

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

What it is: CVE-2025-56803 is a high-severity command injection vulnerability in n/a, published on 3 Sep 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-56803 exists.

Affected product: n/a. 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-56803/ (Markdown: https://insights.sbomify.com/CVE-2025-56803/index.md)
```

## Sources

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

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