dbcve.org
Uncontrolled Search Path (DLL Hijack)Weakness · CWE-427

CVE-2025-14498

HIGH · 7.8 CVSS v3.0 Published 2025-12-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
TradingView Desktop Electron Uncontrolled Search Path Local Privilege Escalation Vulnerability. This vulnerability allows local attackers to escalate privileges on affected installations of TradingView Desktop. An attacker must first obtain the ability to execute low-privileged code on the target system in order to exploit this vulnerability. The specific flaw exists within the configuration of the Electron framework. The product loads a script file from an unsecured location. An attacker can leverage this vulnerability to escalate privileges and execute arbitrary code in the context of a target user. Was ZDI-CAN-27395.

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

TradingView Desktop (Electron-based) loads a script from an unsecured location due to improper configuration of the Electron framework. An attacker with low-privileged code execution can place a malicious script in the application's search path, which then gets executed with elevated privileges when the application runs, achieving local privilege escalation.

MitigationApply the vendor patch when available; until then, restrict write access to directories in the application's search path to prevent an attacker from placing malicious scripts.

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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. Confirm TradingView Desktop installation
    Check for TradingView Desktop installation directory (e.g., C:\Program Files\TradingView or %LOCALAPPDATA%\Programs\TradingView). On Windows, look for 'TradingView.exe'; on macOS check /Applications/TradingView.app; on Linux check ~/.local/share/TradingView or /opt/TradingView.
    Affected if TradingView Desktop is installed on the system
  2. Identify installed version
    Right-click TradingView.exe and select Properties, then view Details tab for version information. On macOS, right-click the app and select Get Info. On Linux, check the version file in the application directory.
    Affected if Version cannot be determined or falls within an unpatched release range
  3. Check for world-writable directories in application path
    Review directory permissions on the TradingView installation folder and its subdirectories. Use 'icacls' on Windows or 'ls -la' on Unix-like systems to identify directories where the Everyone or Users group has Write permissions.
    Affected if Any directory in the application's search path is writable by low-privileged users
  4. Inspect application search path for unexpected scripts
    Search for .js, .ts, .mjs, or .cjs files in the TradingView application directory and parent directories. Check common locations such as the application root, resources folder, and user data directories. Use 'dir /s /b *.js' on Windows or 'find . -name "*.js"' on Unix-like systems.
    Affected if Unexpected or unauthorized script files exist in directories the application searches for scripts
  5. Review Electron security configuration
    If accessible, examine the main.js, preload.js, or equivalent entry point files in the application resources. Look for nodeIntegration: true, contextIsolation: false, or sandbox: false settings which may indicate insecure configuration.
    Affected if Electron security settings allow arbitrary script execution from untrusted locations

A user is affected if TradingView Desktop is installed with writable directories in its search path that allow low-privileged users to place malicious scripts, enabling 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor patch when available; until then, restrict write access to directories in the application's search path to prevent an attacker from placing malicious scripts.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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