Crestron Automate VX up to 6.4.0.49 Network API information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in Crestron Automate VX up to 6.4.0.49. This affects an unknown part of the component Network API. Executing a manipulation can lead to information disclosure. This vulnerability is tracked as CVE-2025-47418. The attack can be launched remotely. No exploit exists. It is advisable to upgrade the affected component.
Details
A vulnerability was found in Crestron Automate VX up to 6.4.0.49. It has been declared as problematic. This vulnerability affects an unknown functionality of the component Network API. The manipulation with an unknown input leads to a information disclosure vulnerability. The CWE definition for the vulnerability is CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. As an impact it is known to affect confidentiality. CVE summarizes:
Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Crestron Automate VX allows Functionality Misuse. There is no visible indication when the system is recording and recording can be enabled remotely via a network API. This issue affects Automate VX: from 5.6.8161.21536 through 6.4.0.49.
This vulnerability was named CVE-2025-47418 since 05/06/2025. The exploitation appears to be easy. The attack can be initiated remotely. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1592.
Upgrading eliminates this vulnerability. The upgrade is hosted for download at crestron.com.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
- 6.4.0.0
- 6.4.0.1
- 6.4.0.2
- 6.4.0.3
- 6.4.0.4
- 6.4.0.5
- 6.4.0.6
- 6.4.0.7
- 6.4.0.8
- 6.4.0.9
- 6.4.0.10
- 6.4.0.11
- 6.4.0.12
- 6.4.0.13
- 6.4.0.14
- 6.4.0.15
- 6.4.0.16
- 6.4.0.17
- 6.4.0.18
- 6.4.0.19
- 6.4.0.20
- 6.4.0.21
- 6.4.0.22
- 6.4.0.23
- 6.4.0.24
- 6.4.0.25
- 6.4.0.26
- 6.4.0.27
- 6.4.0.28
- 6.4.0.29
- 6.4.0.30
- 6.4.0.31
- 6.4.0.32
- 6.4.0.33
- 6.4.0.34
- 6.4.0.35
- 6.4.0.36
- 6.4.0.37
- 6.4.0.38
- 6.4.0.39
- 6.4.0.40
- 6.4.0.41
- 6.4.0.42
- 6.4.0.43
- 6.4.0.44
- 6.4.0.45
- 6.4.0.46
- 6.4.0.47
- 6.4.0.48
- 6.4.0.49
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CNA CVSS-B Score: 🔍
CNA CVSS-BT Score: 🔍
CNA Vector: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: crestron.com
Timeline
05/06/2025 🔍05/07/2025 🔍
05/07/2025 🔍
05/07/2025 🔍
Sources
Status: ConfirmedCVE: CVE-2025-47418 (🔍)
GCVE (CVE): GCVE-0-2025-47418
GCVE (VulDB): GCVE-100-307672
Entry
Created: 05/07/2025 07:01Changes: 05/07/2025 07:01 (67)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.