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

> Attackers can execute arbitrary system commands via unsanitized file paths in the GIF compression tool of MyScreenTools.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Nov 2025
- **Updated:** 17 Nov 2025
- **Also known as:** GHSA-6jrg-fg6f-m23w

## What is CVE-2025-63916?

CVE-2025-63916 is a high-severity command injection vulnerability in n/a, published on 17 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

MyScreenTools v2.2.1.0 contains a critical OS command injection vulnerability in the GIF compression tool. The application fails to properly sanitize user-supplied file paths before passing them to cmd.exe, allowing attackers to execute arbitrary system commands with the privileges of the user running the application. The vulnerability exists in the CMD() function within GIFSicleTool\Form_gif_sicle_tool.cs, which constructs shell commands by concatenating unsanitized user input (file paths) and executes them via cmd.exe.

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

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

It affects 1 product.


Products: Luotengyuan Myscreentools.

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

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

## Is CVE-2025-63916 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63916 is a high-severity command injection vulnerability in n/a, published on 17 Nov 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63916 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-63916/ (Markdown: https://insights.sbomify.com/CVE-2025-63916/index.md)
```

## Sources

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

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