dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-47415

MEDIUM · 6.8 CVSS v4.0 Published 2025-09-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable

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
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in CRESTRON TOUCHSCREENS x70 allows Relative Path Traversal.This issue affects TOUCHSCREENS x70: from 3.000.0110.001 before 3.001.0031.001. Confirmed Affected Hardware: TSW-760, TSW-1060 Confirmed Affected Firmware: 3.002.1061 - (no fix released, product discontinued)   For x70   The Affected Firmware:- 3.000.0110.001  and versions below The Fixed Firmware:- 3.001.0031.001

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 · high confidence

Path traversal vulnerability in Crestron TSW-760 and TSW-1060 touchscreens allows attackers to access files outside restricted directories via relative path traversal (e.g., ../../etc/passwd). Affected firmware versions are 3.000.0110.001 through before 3.001.0031.001, with confirmed affected version 3.002.1061 having no fix released as the product is discontinued.

MitigationSince firmware 3.002.1061 has no patch available (product discontinued), implement network segmentation and restrict access to these devices via firewall rules or VLAN isolation to limit exposure to this medium-severity path traversal.

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
High
Authentication
X
User interaction
P
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:P/VC:N/VI:H/VA:N/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 Crestron touchscreen models on the network
    Inventory network devices to locate TSW-760 or TSW-1060 touchscreens. These are typically found on building automation or AV networks.
    Affected if Any TSW-760 or TSW-1060 device is present on the network
  2. Determine the firmware version installed
    Access the device administration interface or use the manufacturer's method to retrieve the current firmware version (e.g., via web UI, console, or management software).
    Affected if The installed firmware version cannot be determined or is one of the affected versions
  3. Compare firmware version against affected range
    Check if the installed version is 3.000.0110.001 or higher, but lower than 3.001.0031.001, or if it is exactly version 3.002.1061.
    Affected if Version falls within 3.000.0110.001 to 3.001.0031.001 (exclusive of upper bound) OR version is exactly 3.002.1061
  4. Assess network exposure of the web interface
    Determine if the device web administration interface is accessible from untrusted network segments (such as the general corporate network or internet).
    Affected if The device web interface is reachable from outside the immediate local segment without firewall restrictions

A user is affected if they have a TSW-760 or TSW-1060 running firmware version 3.000.0110.001 through 3.001.0031.000, or version 3.002.1061, with the device accessible on the network.

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

Since firmware 3.002.1061 has no patch available (product discontinued), implement network segmentation and restrict access to these devices via firewall rules or VLAN isolation to limit exposure to this medium-severity path traversal.

Recommended fix High confidence

3.001.0031.001

  1. Identify the exact model number (TSW-760 or TSW-1060) of the affected Crestron touchscreen device
  2. Access the device's web interface or use Crestron's firmware update tools to check the current firmware version
  3. If the device is running firmware version 3.000.0110.001 or any version before 3.001.0031.001, proceed with upgrade
  4. Download the firmware version 3.001.0031.001 from the official Crestron support website (security.crestron.com or www.crestron.com)
  5. Follow Crestron's standard firmware update procedure for TSW-x70 series touchscreens
  6. After upgrade, verify the firmware version has been successfully updated to 3.001.0031.001
  7. Note: If the device is running firmware 3.002.1061, be aware this model has been discontinued with no fix available - consider replacement
Caveat TSW-760 and TSW-1060 units running firmware 3.002.1061 are discontinued with no fix available - these units require hardware replacement

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-47415 — 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-47415 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