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

Goal: 1000 CNY · Raised: 1336 CNY

100%
Buy Us a Coffee

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

3786 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, AvailabilityExecute 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.
IntegrityModify 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 …
ConfidentialityRead 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…
AvailabilityDoS: 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)
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…
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.
ImplementationInputs 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 DesignUse 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].
OperationUse 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 IDTitleCVSSSeverityPublished
CVE-2025-21623 ClipBucket V5 Unauthenticated Template Directory Update to Denial-of-Service — clipbucket-v5 7.5 High2025-01-07
CVE-2025-21622 ClipBucket V5 Avatar URL Path Traversal to Arbitrary File Delete — clipbucket-v5 7.5 High2025-01-07
CVE-2024-12425 Path traversal leading to arbitrary .ttf file write — LibreOffice 6.2 -2025-01-07
CVE-2024-56286 WordPress Classic Addons – WPBakery Page Builder plugin <= 3.0 - Local File Inclusion vulnerability — Classic Addons – WPBakery Page Builder 7.5 High2025-01-07
CVE-2024-12152 MIPL WC Multisite Sync <= 1.1.5 - Unauthenticated Arbitrary File Download — MIPL Multistore Sync for WooCommerce. Sync Products, Stock and Orders. 7.5 High2025-01-07
CVE-2024-12849 Error Log Viewer By WP Guru <= 1.0.1.3 - Missing Authorization to Unauthenticated Arbitrary File Read — Error Log Viewer By WP Guru 7.5 High2025-01-07
CVE-2024-41765 IBM Engineering Lifecycle Optimization - Publishing directory traversal — Engineering Lifecycle Optimization Publishing 6.5 Medium2025-01-04
CVE-2024-56514 Karmada Tar Slips in CRDs archive extraction — karmada 8.8 -2025-01-03
CVE-2024-56248 WordPress WPMasterToolKit plugin <= 1.13.1 - Arbitrary File Download vulnerability — WPMasterToolKit 4.9 Medium2025-01-02
CVE-2024-56198 path-sanitizer allows bypassing the existing filters to achieve path-traversal vulnerability — path-sanitizer 7.5 -2024-12-31
CVE-2024-12105 WhatsUp Gold - SnmpExtendedActiveMonitor path traversal — WhatsUp Gold 6.5 Medium2024-12-31
CVE-2024-11944 iXsystems TrueNAS CORE tarfile.extractall Directory Traversal Remote Code Execution Vulnerability — TrueNAS CORE 8.8 -2024-12-30
CVE-2024-12850 Database Backup and check Tables Automated With Scheduler 2024 <= 2.32 - Authenticated (Admin+) Arbitrary File Read — Database Backup and Table Integrity Check with Automated Scheduling 4.9 Medium2024-12-24
CVE-2024-41887 Arbitrary File Overwrite — XRN-420S 9.8 -2024-12-24
CVE-2024-53961 ColdFusion | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (CWE-22) — ColdFusion 8.1 High2024-12-23
CVE-2024-55947 Gogs has a Path Traversal in file update API — gogs 8.8 -2024-12-23
CVE-2024-56331 Local File Inclusion (LFI) via Improper URL Handling in uptime-kuma's `Real-Browser` monitor — uptime-kuma 6.8 Medium2024-12-20
CVE-2024-12830 Arista NG Firewall custom_handler Directory Traversal Remote Code Execution Vulnerability — NG Firewall 9.8 -2024-12-20
CVE-2024-12793 PbootCMS IndexController.php path traversal — PbootCMS 4.3 Medium2024-12-19
CVE-2024-38819 VMware Spring Framework 安全漏洞 — Spring Framework 7.5 High2024-12-19
CVE-2024-21547 Browsershot 安全漏洞 — spatie/browsershot 7.5 High2024-12-18
CVE-2024-56142 Path Traversal in pghoard — pghoard 6.5 -2024-12-17
CVE-2024-54374 WordPress Sogrid plugin <= 1.5.6 - Local File Inclusion vulnerability — Sogrid 7.5 High2024-12-16
CVE-2024-54375 WordPress Woolook plugin <= 1.7.0 - Local File Inclusion vulnerability — Woolook 7.5 High2024-12-16
CVE-2024-54382 WordPress Bold Page Builder plugin <= 5.1.5 - Path Traversal vulnerability — Bold Page Builder 4.9 Medium2024-12-16
CVE-2024-54380 WordPress WP Cookies Enabler plugin <= 1.0.1 - Local File Inclusion vulnerability — WP Cookies Enabler 7.5 High2024-12-16
CVE-2024-54373 WordPress EduAdmin Booking plugin <= 5.2.0 - Local File Inclusion vulnerability — EduAdmin Booking 7.5 High2024-12-16
CVE-2024-12362 InvoicePlane invoices.php download path traversal — InvoicePlane 4.3 Medium2024-12-16
CVE-2024-54259 WordPress DELUCKS SEO plugin <= 2.7.0 - Arbitrary File Download vulnerability — DELUCKS SEO 6.5 Medium2024-12-13
CVE-2024-11834 Arbitrary File Write via PTRAC Import — PlexTrac 7.5 -2024-12-13

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