dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2025-47420

HIGH · 8.7 CVSS v4.0 Published 2025-05-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
266 vulnerability in Crestron Automate VX allows Privilege Escalation.This issue affects Automate VX: from 5.6.8161.21536 through 6.4.0.49.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A privilege escalation vulnerability exists in Crestron Automate VX audio/video control system. An authenticated attacker can escalate privileges to gain higher-level access within the system. The vulnerability affects versions 5.6.8161.21536 through 6.4.0.49.

MitigationUpgrade Crestron Automate VX to a version beyond 6.4.0.49 once a patched release is available from the vendor. Until then, restrict network access to the Automate VX management interfaces to trusted personnel only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the system as Crestron Automate VX
    Locate the device or software product name in the system inventory, management console, or device web interface. Confirm the product is Crestron Automate VX.
    Affected if The system is not Crestron Automate VX, this CVE does not apply.
  2. Determine the installed software version
    Access the Automate VX management interface (web UI or CLI) and navigate to the About, System Info, or Version section to retrieve the firmware/software version number.
    Affected if Unable to retrieve a version number prevents comparison to the affected range.
  3. Compare version to affected range
    Check if the installed version falls between 5.6.8161.21536 and 6.4.0.49 inclusive. Versions at or below 5.6.8161.21536 and above 6.4.0.49 are not in the affected range.
    Affected if The installed version is 5.6.8161.21536 or higher AND 6.4.0.49 or lower.
  4. Verify authentication is enabled and accessible
    Confirm that user authentication is configured on the Automate VX system and that management interfaces (web, API, or CLI) are network-accessible. Check user account existence in the local user database or directory integration settings.
    Affected if No local or directory user accounts exist or management interfaces are not network-accessible, the privilege escalation path may not be reachable.
  5. Confirm presence of lower-privilege accounts
    Review the list of user accounts in the Automate VX user management section. Identify accounts that do not have administrator-level privileges.
    Affected if No non-administrator accounts exist, the privilege escalation from lower to higher privilege may not be exploitable.

The system is affected if it is Crestron Automate VX with a version between 5.6.8161.21536 and 6.4.0.49 inclusive, and the management interface is accessible to authenticated users who could exploit the privilege escalation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Crestron Automate VX to a version beyond 6.4.0.49 once a patched release is available from the vendor. Until then, restrict network access to the Automate VX management interfaces to trusted personnel only.

Recommended fix Moderate confidence

Any version of Crestron Automate VX newer than 6.4.0.49 (contact Crestron for specific fixed release)

  1. 1. Identify the current installed version of Crestron Automate VX by accessing the system administration interface or checking system information.
  2. 2. Confirm the installed version falls within the affected range: 5.6.8161.21536 through 6.4.0.49.
  3. 3. Contact Crestron technical support or visit the official Crestron support portal at www.crestron.com to obtain the latest fixed version of Automate VX.
  4. 4. Before upgrading, review release notes for any prerequisites, compatibility requirements, or migration considerations.
  5. 5. Back up the current system configuration and any critical data according to best practices.
  6. 6. Apply the upgrade to a version newer than 6.4.0.49, preferably the most recent stable release available from Crestron.
  7. 7. After upgrading, verify the system operates normally and confirm the vulnerability is resolved.
Caveat Review release notes for any configuration or feature changes between your current version and the target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47420 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-47420 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data