CVE
Cloud Cmd auth bypass and path traversal in /rename endpoint
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 19.21.4
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 19.21.4.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 36/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Cloud Commander (cloudcmd) is affected. Remote attackers who do not log in can send a PUT /rename request that bypasses authentication and uses absolute or ../ paths to move files outside the configured root, which can cause data loss or denial of service.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Original description
Cloud Commander (cloudcmd) before 19.21.4 contains an authentication bypass and path traversal vulnerability that allows unauthenticated attackers to rename files by sending PUT /rename requests handled before authentication middleware. Attackers can supply absolute or ../ paths in the from and to arrays to move any file the Node.js process can access outside the configured root, causing data loss or denial of service.
Who should check
Anyone running coderaiser cloudcmd (npm package) before 19.21.4, including deployments that use --auth or --root.
“Cloud Commander (cloudcmd) before 19.21.4”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach10/20Affects npm packages
- Severity8.8/10CVSS 8.8
- No patch0/5No signal
What would change the score
- Would score about 81 if added to CISA KEV
- Would score about 76 if CISA's SSVC rates exploitation active
- Would score about 41 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 19.21.4.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130072 (Cloud Commander before 19.21.4 Authentication Bypass and Path Traversal via PUT /rename), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130072 (entry last updated 2026-11-16):
Affected:
- npm package cloudcmd: fixed in 19.21.4
Fixed versions: 19.21.4.
Conditions (all must be true for the bug to be hit):
- Cloud Commander (cloudcmd) versions before 19.21.4 (source: https://www.vulncheck.com/advisories/cloud-commander-before-19.21.4-authentication-bypass-and-path-traversal-via-put-rename)
- Server is run with authentication enabled (--auth), which the bypass defeats (source: https://github.com/coderaiser/cloudcmd/issues/486)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-130072 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130072 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/coderaiser/cloudcmd/commit/25f496ff1c0d512354de92cb7f76c6e86c16aa8f
- https://github.com/coderaiser/cloudcmd/issues/486
- https://github.com/coderaiser/cloudcmd/releases/tag/v19.21.4
- https://github.com/coderaiser/cloudcmd/blob/v19.21.2/server/cloudcmd.js#L253-L258
- https://www.vulncheck.com/advisories/cloud-commander-before-19.21.4-authentication-bypass-and-path-traversal-via-put-rename
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130072
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130072"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- cloudcmdnpm
fixed in 19.21.4
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Patch
- Report
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130072
Is CVE-2026-130072 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The PUT /rename endpoint in Cloud Commander does not properly check authentication or paths, so an unauthenticated attacker can move or rename any file the Node.js process can access outside the configured root. This can cause data loss or denial of service.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-130072?
cloudcmd (npm): before 19.21.4.Source: cve.now feed data
Am I affected, and how do I check?
Cloud Commander (cloudcmd) versions before 19.21.4 are affected, including when the server runs with authentication enabled via --auth, since the bypass defeats it. To check a installed version, look at the version in the package.json of the installed cloudcmd package or run the cloudcmd version command.Source: vulncheck.com, github.com
How do I fix CVE-2026-130072?
Upgrade cloudcmd to version 19.21.4 or later, which is the fixed version named in the advisory.Source: vulncheck.com, github.com