Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-82460 – Path Traversal Enabling Arbitrary File Read/Write (Potential RCE) – Cloud Commander

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-82460 is a critical path traversal vulnerability in Cloud Commander, a web-based file manager, affecting all versions before 19.20.2. The flaw resides in the REST file-operation and markdown endpoints, which fail to properly validate path normalization, allowing attackers to read, write, move, or copy files outside the application’s configured root directory. The vulnerability carries a CVSS v3.1 base score of 9.8 (Critical) and a CVSS v4.0 score of 9.3.

Technical details

  • Root cause: The application’s REST file-operation and markdown endpoints do not properly sanitize or resolve path traversal sequences (e.g., ../) supplied in file path parameters before performing filesystem operations.
  • Trigger conditions: An attacker sends a crafted request to a REST file-operation endpoint (move, copy, pack, extract) or markdown endpoint, embedding directory traversal sequences (including URL-encoded variants such as ..%2f..%2f..%2f) in the source or destination path parameter.
  • Attack vector: Network — the CVSS vector (AV:N/AC:L/PR:N/UI:N) indicates the vulnerability is remotely exploitable over the network with low attack complexity and no user interaction required.
  • Impact: Successful exploitation allows an attacker to escape the configured root/sandbox directory to read, write, move, or copy arbitrary files on the underlying filesystem, which can lead to disclosure of sensitive files or, in write/move scenarios, tampering with application or system files.

Affected software

  • Cloud Commander (npm package cloudcmd), all versions prior to 19.20.2

Severity

  • CVSS v3.1: 9.8 (Critical) — CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0: 9.3 (Critical) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
  • CWE-22: Improper Limitation of a Pathname to a Restricted Directory (‘Path Traversal’)

Mitigation and recommended actions

  • Immediate: Upgrade Cloud Commander to version 19.20.2 or later, which introduces strict path-boundary validation for move, copy, pack, extract, and markdown routing operations.
  • If immediate patching is not possible: Restrict network exposure of Cloud Commander instances (place behind authentication and network access controls, avoid exposing directly to the internet), and monitor/restrict inbound requests to REST file-operation and markdown endpoints for path traversal patterns (e.g., ../, URL-encoded traversal sequences) as an interim compensating control.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Script source URL: /dist/cloudcmd.common.js

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge