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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

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

3432 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-69411 WordPress ionCube tester plus plugin <= 1.3 - Arbitrary File Download vulnerability — ionCube tester plus 7.5 High2026-03-05
CVE-2026-28427 OpenDeck affected by path traversal allows arbitrary file read — OpenDeck 7.5AIHighAI2026-03-04
CVE-2026-0847 Path Traversal in nltk/nltk — nltk/nltk 7.5AIHighAI2026-03-04
CVE-2026-27442 zip_attachments Path Traversal — Secure Email Gateway 7.5AIHighAI2026-03-04
CVE-2026-28769 LFI in /IDC_Logging/checkifdone.cgi, "file" parameter Allowing for File Existence Enumeration On IDC Satellite Receiver Web Management Interface Version 101 — SFX Series SuperFlex Satellite Receiver Web management interface 6.5AIMediumAI2026-03-04
CVE-2026-24848 OpenEMR Arbitrary File Write leading to Remote Code Execution — openemr 8.8AIHighAI2026-03-03
CVE-2026-2606 IBM webMethods API Management fails to validate user input and enables unauthorized arbitrary file read — webMethods API Gateway (on-prem) 6.5 Medium2026-03-03
CVE-2026-28518 OpenViking .ovpack Import ZIP Slip Path Traversal — OpenViking 7.8 High2026-03-03
CVE-2026-2448 Page Builder by SiteOrigin <= 2.33.5 - Authenticated (Contributor+) Local File Inclusion — Page Builder by SiteOrigin 8.8 High2026-03-03
CVE-2026-0655 Path Traversal on TP-Link Deco BE25 — Deco BE25 v1.0 7.3AIHighAI2026-03-02
CVE-2026-3405 thinkgem JeeSite Connection path traversal — JeeSite 3.1 Low2026-03-02
CVE-2026-28406 kaniko has tar archive path traversal in build context extraction allows writing files outside destination directory — kaniko 8.2 High2026-02-27
CVE-2026-27734 Beszel Vulnerable to Docker API Path Traversal via Unsanitized Container ID — beszel 6.5 Medium2026-02-27
CVE-2026-24488 OpenEMR Vulnerable to Arbitrary File Exfiltration via Fax Endpoint — openemr 6.5 Medium2026-02-27
CVE-2026-3223 Zip Slip leading to Arbitrary File Write and Privilege Escalation in Google Web Designer — Web Designer 9.8 -2026-02-27
CVE-2026-2251 Path Traversal leading to Remote Code Execution (RCE) — FreeFlow Core 9.8 Critical2026-02-27
CVE-2026-3289 Sanluan PublicCMS Template Cache Generation TemplateCacheComponent.java saveMetadata path traversal — PublicCMS 6.3 Medium2026-02-27
CVE-2026-22877 Copeland XWEB and XWEB Pro Path Traversal — Copeland XWEB 300D PRO 3.7 Low2026-02-27
CVE-2026-28208 Junrar has arbitrary file write due to backslash path traversal bypass in LocalFolderExtractor on Linux/Unix — junrar 5.9 Medium2026-02-26
CVE-2026-23939 Path Traversal in Local File Store Backend — hexpm 9.1AICriticalAI2026-02-26
CVE-2026-26228 VLC for Android < 3.7.0 Remote Access Path Traversal — VLC for Android 4.9 Medium2026-02-26
CVE-2026-1311 Worry Proof Backup <= 0.2.4 - Authenticated (Subscriber+) Path Traversal via Backup Upload — Worry Proof Backup 8.8 High2026-02-26
CVE-2026-27969 Vitess users with backup storage access can write to arbitrary file paths on restore — vitess 6.5AIMediumAI2026-02-26
CVE-2026-1557 WP Responsive Images <= 1.0 - Unauthenticated Path Traversal to Arbitrary File Read via src — WP Responsive Images 7.5 High2026-02-26
CVE-2026-27884 NetExec vulnerable to arbitrary file write via path traversal in spider_plus module — NetExec 5.3 Medium2026-02-26
CVE-2026-27735 mcp-server-git : Path traversal in git_add allows staging files outside repository boundaries — servers 8.6AIHighAI2026-02-25
CVE-2026-27800 Zed has Zip Slip Path Traversal in Extension Archive Extraction — zed 7.4 High2026-02-25
CVE-2026-27819 Vikunja has Path Traversal in CLI Restore — vikunja 7.2 High2026-02-25
CVE-2026-26985 LORIS vulnerable to path traversal in electrophysiology_browser — Loris 8.1 High2026-02-25
CVE-2026-26984 LORIS media module vulnerable to remote code execution — Loris 8.8AIHighAI2026-02-25

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