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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

400 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-72742 DSPy 3.3.0b1 Local File Read via Image/Audio Output Field Parsing — DSPy 8.6 High2026-08-11
CVE-2026-18127 Ivanti Endpoint Manager <2024 SU7 文件名外部控制漏洞 — Endpoint Manager 7.7 High2026-08-11
CVE-2026-19353 DedeCMS Installation Wizard index.php _4_Setup file inclusion — DedeCMS 5.0 Medium2026-08-09
CVE-2026-54200 TeamDavid: Local File Inclusion via the form field 'scjob' — TeamDavid 8.4 High2026-08-07
CVE-2026-12070 TeamDavid: Arbitrary File Deletion via form field 'scjob' — TeamDavid 8.4 High2026-08-07
CVE-2026-19011 TinyAGI agents.ts buildSystemPrompt file inclusion — TinyAGI 5.3 Medium2026-08-06
CVE-2026-19009 TinyAGI Message API Endpoint response.ts collectFiles file inclusion — TinyAGI 7.3 High2026-08-06
CVE-2026-15307 Server-side file-write and request forgery via spatial lookups — Django 8.8 High2026-08-04
CVE-2026-18806 Arbitrary Block Device Write via Missing Validation in TÜBİTAK BİLGEM's pardus-image-writer — pardus-image-writer 7.1 High2026-08-04
CVE-2026-65802 Microsoft Edge for Android Information Disclosure Vulnerability — Microsoft Edge (Chromium-based) 7.4 High2026-08-03
CVE-2026-66310 Microsoft Edge for Android Information Disclosure Vulnerability — Microsoft Edge for Android 7.7 High2026-08-03
CVE-2026-64816 RapidRAW < 1.6.0 NTLMv2 Credential Leak via UNC Path in lutPath — RapidRAW 6.5 Medium2026-07-30
CVE-2026-56390 Arbitrary Output Location Change in GNU Bison — Bison 4.6 Medium2026-07-29
CVE-2026-57916 Arbitrary Path Execution via CPS URI in proCertum SmartSign — proCertum SmartSign 4.6 Medium2026-07-27
CVE-2026-65896 Grav API Plugin before 1.0.10 Path Traversal via move — grav 7.1 High2026-07-23
CVE-2026-45139 CI4MS Fileeditor allows deletion and rename of critical application files due to missing extension allowlist on destructive operations — ci4ms 6.5 Medium2026-07-20
CVE-2026-50162 oras-go: file store write outside workingDir via symlink traversal — oras-go--2026-07-17
CVE-2026-9587 Authenticated Local File Inclusion (LFI) in Switchvox SMB Web Portal — Switchvox SMB Edition--2026-07-17
CVE-2026-44019 Docling Core has insufficient validation of image reference URIs — docling-core 8.1 High2026-07-16
CVE-2026-50148 Metabase: Remote Code Execution via Snowflake JDBC Driver Arbitrary File Write — metabase 10.0 Critical2026-07-15
CVE-2026-61873 Grav before 9.1.8 Arbitrary File Write via Twig-Processed Filename — grav 8.1 High2026-07-15
CVE-2026-50462 Windows Ancillary Function Driver for WinSock Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.8 High2026-07-14
CVE-2026-54108 Microsoft SharePoint Server Spoofing Vulnerability — Microsoft SharePoint Enterprise Server 2016 6.5 Medium2026-07-14
CVE-2026-55002 Microsoft SQL Server Elevation of Privilege Vulnerability — Microsoft SQL Server 2016 Service Pack 3 (GDR) 8.8 High2026-07-14
CVE-2026-61462 mcp-gitlab Path Traversal via job_id Parameter — mcp-gitlab 8.6 High2026-07-13
CVE-2026-14480 OpenPLC v3 External Control of File Name or Path — OpenPLC 9.9 Critical2026-07-10
CVE-2026-53449 Coturn: Arbitrary File Write via CLI psd Command — coturn 6.0 Medium2026-07-10
CVE-2026-59793 JetBrains TeamCity 输入验证错误漏洞 — TeamCity 8.8 High2026-07-10
CVE-2026-59807 Composio SDK < 0.2.32-beta.283 - Sensitive File Upload via tool-file-uploads.ts — composio 6.8 Medium2026-07-08
CVE-2026-59819 LiteLLM: Local file read via request-supplied OIDC file references — litellm--2026-07-08

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