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

Goal: 1000 CNY · Raised: 1359 CNY

100%

CWE-22 (对路径名的限制不恰当(路径遍历)) — Vulnerability Class 5191

5191 vulnerabilities classified as CWE-22 (对路径名的限制不恰当(路径遍历)). AI Chinese analysis included.

CWE-22 represents a critical input validation weakness where software fails to properly sanitize external input before constructing file paths. Attackers typically exploit this vulnerability by injecting directory traversal sequences, such as “../”, into user-supplied parameters. These malicious inputs allow the application to resolve file references outside the intended restricted directory, potentially granting unauthorized access to sensitive system files, configuration data, or source code. To mitigate this risk, developers must implement rigorous input validation techniques, ensuring that all path components are strictly checked against allowed characters and structures. Additionally, employing canonicalization to resolve symbolic links and relative paths before validation, combined with strict chroot jails or sandboxing, effectively confines file operations to designated directories, thereby neutralizing the potential for path traversal attacks and preserving system integrity.

MITRE CWE Description
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. Many file operations are intended to take place within a restricted directory. By using special elements such as ".." and "/" separators, attackers can escape outside of the restricted location to access files or directories that are elsewhere on the system. One of the most common special elements is the "../" sequence, which in most modern operating systems is interpreted as the parent directory of the current location. This is referred to as relative path traversal. Path traversal also covers the use of absolute pathnames such as "/usr/local/bin" to access unexpected files. This is referred to as absolute path traversal.
Common Consequences (4)
Integrity, Confidentiality, Availability Execute Unauthorized Code or Commands
The attacker may be able to create or overwrite critical files that are used to execute code, such as programs or libraries.
Integrity Modify Files or Directories
The attacker may be able to overwrite or create critical files, such as programs, libraries, or important data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, appending a new account at the end of a password file may allow …
Confidentiality Read Files or Directories
The attacker may be able read the contents of unexpected files and expose sensitive data. If the targeted file is used for a security mechanism, then the attacker may be able to bypass that mechanism. For example, by reading a password file, the attacker could conduct brute force password guessing a…
Availability DoS: Crash, Exit, or Restart
The attacker may be able to overwrite, delete, or corrupt unexpected critical files such as programs, libraries, or important data. This may prevent the product from working at all and in the case of protection mechanisms such as authentication, it has the potential to lock out product users.
Mitigations (5)
Implementation Assume 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…
Architecture and Design For 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.
Implementation Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked. Use a built-in path canonicalization function (such as realpath(…
Architecture and Design Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
Operation Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth [REF-1481].
Effectiveness: Moderate
Examples (2)
The following code could be for a social networking application in which each user's profile information is stored in a separate file. All files are stored in a single directory.
my $dataPath = "/users/cwe/profiles"; my $username = param("user"); my $profilePath = $dataPath . "/" . $username; open(my $fh, "<", $profilePath) || ExitError("profile read error: $profilePath"); print "<ul>\n"; while (<$fh>) { print "<li>$_</li>\n"; } print "</ul>\n";
Bad · Perl
../../../etc/passwd
Attack
In the example below, the path to a dictionary file is read from a system property and used to initialize a File object.
String filename = System.getProperty("com.domain.application.dictionaryFile"); File dictionaryFile = new File(filename);
Bad · Java
CVE ID Title CVSS Severity Published
CVE-2026-106490 Backstage: Improper input validation in TechDocs static content requests — backstage 6.5 Medium 2026-10-06
CVE-2026-106489 Backstage: Improper authorization enforcement for TechDocs static content — backstage 6.5 Medium 2026-10-06
CVE-2026-106486 Backstage: Improper filesystem validation in Bitbucket pull-request scaffolder actions — backstage 8.5 High 2026-10-06
CVE-2026-101155 Security Advisory 0189 — CloudVision Portal 9.1 Critical 2026-10-06
CVE-2026-101154 Security Advisory 0189 — CloudVision Portal 7.2 High 2026-10-06
CVE-2026-101153 Security Advisory 0188 — CloudVision Portal 8.0 High 2026-10-06
CVE-2026-86360 Dell System Update<2.3.0.0路径遍历致根权限RCE — System Update 9.6 Critical 2026-10-06
CVE-2026-71168 Dell System Update<2.3.0.0路径穿越致远程执行 — System Update 7.3 High 2026-10-06
CVE-2026-106109 Quasar Framework: App Vite build cleanup can recursively remove unsafe configured output directories — quasar 4.1 Medium 2026-10-06
CVE-2026-106103 Quasar Framework: Path Traversal / Arbitrary File Write via crafted Icon Genie profile — quasar 7.1 High 2026-10-06
CVE-2026-105865 Payload: Incomplete validation during the upload file lifecycle — payload 8.1 High 2026-10-06
CVE-2026-105795 Kiota: Unsafe oauth_card_path references in Kiota-generated API plugin manifests — kiota 3.1 Low 2026-10-06
CVE-2026-105840 lrzsz before 0.13.0 Path Traversal via lrz Restricted Mode checkpath() — lrzsz 7.5 High 2026-10-06
CVE-2026-105834 Rundeck before 6.2.0 Arbitrary File Read via File Resource Model Source — rundeck 6.5 Medium 2026-10-06
CVE-2026-39792 WordPress Simple File List plugin <= 6.3.11 - Arbitrary File Deletion vulnerability — Simple File List 8.6 High 2026-10-06
CVE-2026-39754 WordPress Piotnet Addons For Elementor plugin <= 7.1.71 - Arbitrary File Download vulnerability — Piotnet Addons For Elementor 6.5 Medium 2026-10-06
CVE-2026-39752 WordPress Jobs for WordPress plugin <= 2.8.2 - Arbitrary File Deletion vulnerability — Jobs for WordPress 7.7 High 2026-10-06
CVE-2026-105751 Docling: Arbitrary local file read via draw:image xlink:href in the OpenDocument backend — docling 6.9 Medium 2026-10-05
CVE-2026-105744 Docling: Arbitrary file read/write (and command execution when shell-escape is enabled) when rendering untrusted TikZ with the opt-in Tectonic engine — docling 7.5 High 2026-10-05
CVE-2026-105677 Ghost: Remote Code Execution via Theme Translation Files — Ghost 7.2 High 2026-10-05
CVE-2026-105676 Ghost: Path Traversal via Locale Setting — Ghost 4.9 Medium 2026-10-05
CVE-2026-89039 Arbitrary file read via the convert_playwright_script prompt in mcp-k6 — mcp-k6 6.5 Medium 2026-10-05
CVE-2026-63266 Arbitrary file write via calcext:data-mappings, sql provider and Firebird backup functionality — LibreOffice 6.8 Medium 2026-10-05
CVE-2026-105286 Totolink A3002MU File Upload formUploadFile sub_44B250 path traversal — A3002MU 6.3 Medium 2026-10-05
CVE-2026-104805 Mitel MiVoice Office 400 Backup Restoration Arbitrary File Write Leading to Root Code Execution — Mitel MiVoice Office 400 8.5 High 2026-10-05
CVE-2026-105293 Legcord 1.1.0 through 1.3.0 Path Traversal via Theme IPC Handlers — Legcord 8.1 High 2026-10-05
CVE-2026-105174 Gerapy Project Management views.py project_create path traversal — Gerapy 5.4 Medium 2026-10-05
CVE-2026-105157 RainyGao DocSys Document Controller doGetTmpFile.do DocController.doGetTmp path traversal — DocSys 4.3 Medium 2026-10-04
CVE-2026-105144 Drogon Static File Router StaticFileRouter.cc route path traversal — Drogon 5.3 Medium 2026-10-04
CVE-2026-105125 LaraDashboard before 1.4.8 Path Traversal via /api/translations/{lang} Endpoint — laradashboard 3.7 Low 2026-10-03

Vulnerabilities classified as CWE-22 (对路径名的限制不恰当(路径遍历)) represent 5191 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.