CVE-2026-45230: DumbAssets 1.0.11 Path Traversal File Deletion via /api/delete-file
DumbAssets through 1.0.11 contains a path traversal vulnerability in the POST /api/delete-file endpoint and filesToDelete array parameters that allows unauthenticated attackers to delete arbitrary files by supplying ../ sequences that bypass directory boundary validation. Attackers can exploit the optional and disabled-by-default authentication control to traverse outside the intended application directory and delete critical files such as server.js or package.json, causing complete denial of service.
Security readout for executives and security teams
Plain-English summary
DumbAssets through 1.0.11 has a critical flaw that can let an unauthenticated remote attacker delete files outside the intended upload or asset directory. Deleting application files such as server.js or package.json could take the service offline. The provided sources do not show active exploitation or a confirmed patched release.
Executive priority
Treat as urgent for any exposed DumbAssets deployment. The primary business risk is service outage from remote file deletion, not data theft based on the provided CVSS and description.
Technical view
The issue is a CWE-22 path traversal in POST /api/delete-file through filesToDelete array handling. Directory boundary validation can be bypassed with traversal sequences, allowing arbitrary file deletion. CVSS is 9.1 because network, no-auth exploitation can cause high integrity and availability impact without user interaction.
Likely exposure
Exposure is likely limited to organizations running DumbWareio DumbAssets through 1.0.11, especially instances where /api/delete-file is reachable over the network and authentication is disabled or not enforced.
Exploitation context
The source bundle describes unauthenticated arbitrary file deletion and denial of service potential. CISA KEV is false, and the provided sources do not establish active exploitation in the wild.
Researcher notes
Evidence is strong for affected behavior and severity, but incomplete for exploit prevalence and final remediation. Avoid assuming a patch exists solely from the referenced pull request; confirm vendor release guidance before closing exposure.
Mitigation direction
Check DumbWareio and VulnCheck guidance for a vendor-confirmed fixed version.
Restrict public access to POST /api/delete-file immediately.
Enable available authentication controls, but do not treat that as a complete fix.
Back up critical application files and deployment manifests.
Monitor for unexpected deletion of application files.
Validation and detection
Inventory all DumbAssets deployments and confirm versions through 1.0.11.
Verify whether /api/delete-file is reachable without authentication.
Review application logs for suspicious POST /api/delete-file activity.
Confirm server.js, package.json, and other critical files remain intact.
Track PR 136 and advisory updates for remediation status.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-22 · source CWE mapping
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.