# CVE-2025-47417: Enable Debug Images

> Enabling debug images in Crestron Automate VX stores video snapshots locally without user indication, exposing sensitive visual data to unauthorized actors.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 May 2025
- **Updated:** 8 May 2025
- **Also known as:** GHSA-rfm8-87pc-cwp6

## What is CVE-2025-47417?

CVE-2025-47417 is a medium-severity vulnerability in Crestron Automate VX, published on 6 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Crestron Automate VX allows Functionality Misuse.

When Enable Debug Images in Crestron Automate VX is active, snapshots of the captured video or portions thereof are stored locally on the system, and there is no visible indication that this is being done.

This issue affects Automate VX: from 5.6.8161.21536 through 6.4.0.49.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2025-47417 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-47417 is a medium-severity vulnerability in Crestron Automate VX, published on 6 May 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47417 exists.

Affected product: Crestron Automate VX. 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-47417/ (Markdown: https://insights.sbomify.com/CVE-2025-47417/index.md)
```

## Sources

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

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