Skip to main content
VulnerabilityPublished

CVE-2025-63680: Path Traversal

Source CVE Database V5

0

Not known to be exploited · CVSS 8.6 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.6High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 23% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 14 Nov 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

AI-suggested

  1. Monitor for vendor updates and apply patches immediately once released to address the path parsing/UI rendering flaw.
  2. Until patches are available, restrict user ability to click or interact with backup entries that originate from untrusted or external sources.
  3. Educate users about the risk of clicking unexpected or suspicious backup entries, emphasizing caution with UI elements that resemble folders but may be malicious.
  4. Implement application whitelisting and endpoint protection solutions that can detect and block execution of unauthorized scripts or binaries launched via ShellExecuteW.
  5. Use Windows Group Policy to disable or restrict execution of scripts with extensions commonly exploited via PATHEXT fallback (e.g., .BAT, .CMD) in user directories or backup folders.
  6. Employ network segmentation to limit the spread of malware if arbitrary code execution occurs.
  7. Regularly audit backup files and folder structures for anomalous naming patterns such as trailing dots or suspicious scripts.
  8. Enhance logging and monitoring to detect unusual ShellExecuteW invocations or user interactions with backup software UI components.

Description

Nero BackItUp in the Nero Productline is vulnerable to a path parsing/UI rendering flaw (CWE-22) that, in combination with Windows ShellExecuteW fallback extension resolution, leads to arbitrary code execution when a user clicks a crafted entry. By creating a trailing-dot folder and placing a same-basename script, Nero BackItUp renders the file as a folder icon and then invokes ShellExecuteW, which executes the script via PATHEXT fallback (.COM/.EXE/.BAT/.CMD). The issue affects recent Nero BackItUp product lines (2019-2025 and earlier) and has been acknowledged by the vendor.

References

Community reviews

Loading reviews…