Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CWE-73 (文件名或路径的外部可控制) — Vulnerability Class 389

389 vulnerabilities classified as CWE-73 (文件名或路径的外部可控制). AI Chinese analysis included.

CWE-73 represents a critical input validation weakness where applications allow external actors to dictate file system paths, potentially leading to unauthorized access or modification of sensitive data. Attackers typically exploit this vulnerability through path traversal techniques, injecting sequences like “../” to escape intended directories and reach critical system files or application configurations. This manipulation occurs when software fails to sanitize user-supplied input before using it in filesystem operations, allowing the attacker to bypass intended access controls. To mitigate this risk, developers must implement rigorous input validation, ensuring that all file paths are strictly checked against a whitelist of allowed directories. Additionally, using canonicalization functions to resolve paths before comparison and employing chroot jails can effectively isolate file access, thereby preventing attackers from navigating outside the designated application sandbox.

MITRE CWE Description
The product allows user input to control or influence paths or file names that are used in filesystem operations. This could allow an attacker to access or modify system files or other files that are critical to the application. Path manipulation errors occur when the following two conditions are met: 1. An attacker can specify a path used in an operation on the filesystem. 2. By specifying the resource, the attacker gains a capability that would not otherwise be permitted. For example, the program may give the attacker the ability to overwrite the specified file or run with a configuration controlled by the attacker.
Common Consequences (3)
Integrity, ConfidentialityRead Files or Directories, Modify Files or Directories
The application can operate on unexpected files. Confidentiality is violated when the targeted filename is not directly readable by the attacker.
Integrity, Confidentiality, AvailabilityModify Files or Directories, Execute Unauthorized Code or Commands
The application can operate on unexpected files. This may violate integrity if the filename is written to, or if the filename is for a program or other form of executable code.
AvailabilityDoS: Crash, Exit, or Restart, DoS: Resource Consumption (Other)
The application can operate on unexpected files. Availability can be violated if the attacker specifies an unexpected file that the application modifies. Availability can also be affected if the attacker specifies a filename for a large file, or points to a special device or a file that does not hav…
Mitigations (5)
Architecture and DesignWhen the set of filenames is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames, and reject all other inputs. For example, ID 1 could map to "inbox.txt" and ID 2 could map to "profile.txt". Features such as the ESAPI AccessReferenceMap provide this capability.
Architecture and Design, OperationRun your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict all access to files within a particular directory. Examples include the Unix chroot jail and AppArmor. In general, managed code may provide some protection. This may not be a feasible solution, and it only limits the impact to the oper…
Architecture and DesignFor any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
ImplementationAssume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range…
Effectiveness: High
ImplementationUse a built-in path canonicalization function (such as realpath() in C) that produces the canonical version of the pathname, which effectively removes ".." sequences and symbolic links (CWE-23, CWE-59).
Examples (2)
The following code uses input from an HTTP request to create a file name. The programmer has not considered the possibility that an attacker could provide a file name such as "../../tomcat/conf/server.xml", which causes the application to delete one of its own configuration files (CWE-22).
String rName = request.getParameter("reportName"); File rFile = new File("/usr/local/apfr/reports/" + rName); ... rFile.delete();
Bad · Java
The following code uses input from a configuration file to determine which file to open and echo back to the user. If the program runs with privileges and malicious users can change the configuration file, they can use the program to read any file on the system that ends with the extension .txt.
fis = new FileInputStream(cfg.getProperty("sub")+".txt"); amt = fis.read(arr); out.println(arr);
Bad · Java
CVE IDTitleCVSSSeverityPublished
CVE-2026-8095 Frontend File Manager Plugin <= 23.6 - Authenticated (Subscriber+) Arbitrary File Deletion — Frontend File Manager Plugin 8.1 High2026-06-27
CVE-2026-47214 Docling: Unsafe URI and Path Handling in HTML Backend — docling 7.1 High2026-06-26
CVE-2025-71338 Flowise - Arbitrary File Write to Remote Code Execution via document-store API — Flowise 10.0 Critical2026-06-25
CVE-2025-71334 Flowise - Arbitrary File Access via Missing Chat Flow ID Validation — Flowise 9.8 Critical2026-06-25
CVE-2025-71333 Flowise - Arbitrary File Upload via Unauthenticated /api/v1/attachments Endpoint — Flowise--2026-06-25
CVE-2025-71324 Flowise - Arbitrary File Read via chatId Parameter — Flowise 7.5 High2026-06-25
CVE-2026-55477 Authenticated Arbitrary File Write via Database Import and Xray Log Path Manipulation — 3x-ui 7.2 High2026-06-25
CVE-2026-48520 Langflow: Unauthenticated Shareable Playground arbitrary local or S3 file read — langflow 6.1 Medium2026-06-23
CVE-2026-53632 NTLMv2 hash disclosure via UNC path handling on Windows — launch-editor--2026-06-22
CVE-2026-49358 PhpWeasyPrint vulnerable to arbitrary file deletion at shutdown via public $temporaryFiles — php-weasyprint 3.0 Low2026-06-19
CVE-2026-53915 JetBrains GoLand 输入验证错误漏洞 — GoLand 7.1 High2026-06-19
CVE-2026-8118 Royal Addons for Elementor – Addons and Templates Kit for Elementor 1.7.1058 - 1.7.1059 - Authenticated (Contributor+) Arbitrary File Read via Data Table Widget CSV File Source — Royal Addons for Elementor – Addons and Templates Kit for Elementor 6.5 Medium2026-06-19
CVE-2025-52465 GeoServer has an arbitrary file write vulnerability in its Master Password Dump Page — org.geoserver.web:gs-web-app 7.2 High2026-06-18
CVE-2026-2604 Evolution-data-server: evolution data server: arbitrary file deletion via inconsistent uri handling — Evolution Data Server 5.6 Medium2026-06-16
CVE-2026-10303 ServerCo getssl ACME shell script path injection — getssl 7.4 High2026-06-16
CVE-2026-34030 Improper branch-code validation in Wertheim SafeController Software allows file path manipulation — Wertheim SafeController Software for VAULT ROOMS (Safe Deposit Locker System)--2026-06-15
CVE-2026-47643 Azure Stack Edge Remote Code Execution Vulnerability — Azure Stack Edge 9.8 Critical2026-06-09
CVE-2025-12656 Migration, Backup, Staging – WPvivid Backup & Migration <= 0.9.128 - Authenticated (Admin+) Arbitrary Directory Deletion — WPvivid — Backup, Migration & Staging 3.8 Low2026-06-05
CVE-2026-20175 Cisco Finesse File Inclusion Vulnerability — Cisco Finesse 6.1 Medium2026-06-03
CVE-2026-35080 Arbitrary file delete vulnerability in method ugw-restoreinfo — Single-A 8.1 High2026-06-03
CVE-2026-35079 Arbitrary file delete vulnerability in method ugw-restore — Single-A 8.1 High2026-06-03
CVE-2026-35078 Arbitrary file delete vulnerability in method ugw-logstop — Single-A 8.1 High2026-06-03
CVE-2026-35077 Arbitrary file delete vulnerability in method ugw-delete-file — Single-A 8.1 High2026-06-03
CVE-2026-35076 Arbitrary file delete vulnerability in method bac-scanresult — Single-A 8.1 High2026-06-03
CVE-2026-10694 SourceCodester Online Food Ordering System index.php include file inclusion — Online Food Ordering System 7.3 High2026-06-03
CVE-2026-10559 SourceCodester Pizzafy Ecommerce System index.php file inclusion — Pizzafy Ecommerce System 6.3 Medium2026-06-02
CVE-2026-10558 SourceCodester Pizzafy Ecommerce System index.php file inclusion — Pizzafy Ecommerce System 6.3 Medium2026-06-02
CVE-2026-45088 Dalfox: Unauthenticated Arbitrary File Read with Out-of-Band Exfiltration via `custom-payload-file` in Dalfox Server Mode — dalfox 7.5 High2026-05-27
CVE-2026-45089 Dalfox: Unauthenticated Arbitrary File Create/Append via `output` Option in Dalfox Server Mode — dalfox 8.2 High2026-05-27
CVE-2025-0898 Xpro Elementor Addons - Pro <= 1.4.7 - Authenticated (Contributor+) Arbitrary File Read via Draw SVG — Xpro Elementor Addons - Pro 6.5 Medium2026-05-27

Vulnerabilities classified as CWE-73 (文件名或路径的外部可控制) represent 389 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.