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-2026-3188 feiyuchuixue sz-boot-parent API templates path traversal — sz-boot-parent 4.3 Medium2026-02-25
CVE-2026-27704 Dart SDK and Flutter SDK have Zip slip in Dart Pub package extraction — sdk 7.3AIHighAI2026-02-25
CVE-2026-27699 Basic FTP has Path Traversal Vulnerability in its downloadToDir() method — basic-ftp 9.1 Critical2026-02-25
CVE-2026-25785 MOTEX LanScope Endpoint Manager 路径遍历漏洞 — Lanscope Endpoint Manager (On-Premises) Sub-Manager Server 8.8AIHighAI2026-02-25
CVE-2026-3179 A path traversal vulnerability was found in the FTP Backup on the ADM. — ADM 6.5 -2026-02-25
CVE-2026-27606 Rollup 4 has Arbitrary File Write via Path Traversal — rollup 9.9 -2026-02-25
CVE-2026-24849 OpenEMR Arbitrary File Read Vulnerability — openemr 10.0 Critical2026-02-25
CVE-2026-27598 Dagu: Path traversal in DAG creation allows arbitrary YAML file write outside DAGs directory — dagu 8.8 -2026-02-25
CVE-2026-27117 bit7z has a path traversal vulnerability — bit7z 5.5 Medium2026-02-24
CVE-2026-25891 Fiber has an Arbitrary File Read in Static Middleware on Windows — fiber 7.5AIHighAI2026-02-24
CVE-2026-25603 Path Traversal vulnerability in Linksys MR9600, Linksys MX4200 — MR9600 6.8AIMediumAI2026-02-24
CVE-2026-27483 MindsDB has Path Traversal in /api/files Leading to Remote Code Execution — mindsdb 8.8 High2026-02-24
CVE-2025-15589 MuYuCMS Template Management Template.php delete_dir_file path traversal — MuYuCMS 3.8 Low2026-02-24
CVE-2026-3067 HummerRisk Archive Extraction CommandUtils.java extractZip path traversal — HummerRisk 6.3 Medium2026-02-24
CVE-2026-25965 ImageMagick's policy bypass through path traversal allows reading restricted content despite secured policy — ImageMagick 8.6 High2026-02-24
CVE-2026-3051 DataLinkDC dinky Project Name GitRepository.java getProjectDir path traversal — dinky 6.3 Medium2026-02-24
CVE-2026-23521 Traccar vulnerable to Path Traversal and External Control of File Name or Path — traccar 6.5 Medium2026-02-23
CVE-2026-2953 Dromara UJCMS Template WebFileTemplateController.delete deleteDirectory path traversal — UJCMS 5.4 Medium2026-02-22
CVE-2026-2864 feng_ha_ha/megagao ssm-erp/production_ssm PictureController.java pictureDelete path traversal — ssm-erp 5.4 Medium2026-02-21
CVE-2026-2863 feng_ha_ha/megagao ssm-erp/production_ssm FileServiceImpl.java deleteFile path traversal — ssm-erp 5.4 Medium2026-02-21
CVE-2026-2033 MLflow Tracking Server Artifact Handler Directory Traversal Remote Code Execution Vulnerability — MLflow 9.8AICriticalAI2026-02-20
CVE-2026-27115 ADB Explorer is Vulnerable to Arbitrary Directory Deletion via Command-Line Argument — ADB-Explorer 7.1 High2026-02-20
CVE-2026-24953 WordPress Simple File List plugin <= 6.1.15 - Arbitrary File Download vulnerability — Simple File List 6.5 Medium2026-02-20
CVE-2025-69379 WordPress Upload Files Anywhere plugin <= 2.8 - Arbitrary File Deletion vulnerability — Upload Files Anywhere 8.6 High2026-02-20
CVE-2025-69377 WordPress User Extra Fields plugin <= 17.0 - Arbitrary File Deletion vulnerability — User Extra Fields 7.7 High2026-02-20
CVE-2025-69380 WordPress Upload Files Anywhere plugin <= 2.8 - Arbitrary File Download vulnerability — Upload Files Anywhere 7.5 High2026-02-20
CVE-2025-69376 WordPress User Extra Fields plugin <= 17.0 - Arbitrary File Deletion vulnerability — User Extra Fields 8.6 High2026-02-20
CVE-2025-68862 WordPress Woo File Dropzone plugin <= 1.1.7 - Arbitrary File Deletion vulnerability — Woo File Dropzone 7.7 High2026-02-20
CVE-2025-68002 WordPress Open User Map plugin <= 1.4.16 - Arbitrary File Download vulnerability — Open User Map 6.5 Medium2026-02-20
CVE-2026-26065 calibre: Path Traversal can Lead to Arbitrary File Write and Potential Code Execution — calibre 8.8 -2026-02-20

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