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-24969 WordPress Instant VA theme <= 1.0.1 - Arbitrary File Deletion vulnerability — Instant VA 7.7 High2026-03-25
CVE-2026-22448 WordPress PitchPrint plugin <= 11.1.2 - Arbitrary File Deletion vulnerability — PitchPrint 7.5 High2026-03-25
CVE-2026-33344 Dagu has an incomplete fix for CVE-2026-27598: path traversal via %2F-encoded slashes in locateDAG — dagu 8.1 High2026-03-24
CVE-2026-33329 FileRise: Path Traversal in `resumableIdentifier` Leading to Arbitrary File Write, Recursive Directory Deletion, and Limited Existence Oracle — FileRise 8.1 High2026-03-24
CVE-2026-33497 Langflow: /profile_pictures/{folder_name}/{file_name} endpoint file reading — langflow 6.5 -2026-03-24
CVE-2026-33309 Langflow has an Arbitrary File Write (RCE) via v2 API — langflow 10.0 Critical2026-03-24
CVE-2026-4741 Path Traversal Vulnerability in TeamJCD/JoyConDroid — JoyConDroid 8.1 -2026-03-24
CVE-2026-33211 Tekton Pipelines git resolver has path traversal that allows reading arbitrary files from the resolver pod — pipeline 9.6 Critical2026-03-23
CVE-2026-33242 Salvo has a Path Traversal in salvo-proxy::encode_url_path allows API Gateway Bypass — salvo 7.5 High2026-03-23
CVE-2026-33195 Rails Active Storage has possible Path Traversal in DiskService — activestorage 8.8 -2026-03-23
CVE-2025-60946 Census CSWeb path traversal — CSWeb 8.8 High2026-03-23
CVE-2026-23485 Blinko: Unauthorized Path Traversal File Enumeration - music-metadata — blinko 5.3 -2026-03-23
CVE-2026-23481 Blinko: Authenticated Arbitrary File Write - saveAdditionalDevFile — blinko 8.1 -2026-03-23
CVE-2026-23484 Blinko: Authenticated Arbitrary File Write - saveDevPlugin — blinko 6.5 -2026-03-23
CVE-2026-23483 Blinko: Unauthorized Arbitrary File Read - /plugins — blinko--2026-03-23
CVE-2026-23482 Blinko: Unauthorized Arbitrary File Read - /api/file/temp — blinko 5.3 -2026-03-23
CVE-2026-33681 AVideo has Path Traversal in pluginRunDatabaseScript.json.php Enables Arbitrary SQL File Execution via Unsanitized Plugin Name — AVideo 7.2 High2026-03-23
CVE-2026-33513 AVideo has an Unauthenticated Local File Inclusion in API locale (RCE possible with writable PHP) — AVideo 8.6 High2026-03-23
CVE-2026-33493 AVideo has a Path Traversal in import.json.php that Allows Private Video Theft and Arbitrary File Read/Deletion via fileURI Parameter — AVideo 7.1 High2026-03-23
CVE-2026-33293 AVideo Affected by Arbitrary File Deletion via Path Traversal in CloneSite deleteDump Parameter — AVideo 8.1 High2026-03-22
CVE-2026-33292 AVideo has Authorization Bypass via Path Traversal in HLS Endpoint Allows Streaming Private/Paid Videos — AVideo 7.5 High2026-03-22
CVE-2019-25610 NetNumber Titan Master 7.9.1 Path Traversal via drp — NetNumber Titan ENUM/DNS/NP 6.5 Medium2026-03-22
CVE-2026-4542 SSCMS layerImage Endpoint LayerImageController.Submit.cs path traversal — SSCMS 5.4 Medium2026-03-22
CVE-2019-25579 phpTransformer 2016.9 Directory Traversal via jQueryFileUpload — phpTransformer 7.5 High2026-03-21
CVE-2019-25577 SeoToaster Ecommerce 3.0.0 Local File Inclusion via backend_theme — SeoToaster Ecommerce 5.5 Medium2026-03-21
CVE-2019-25574 Green CMS 2.x Path Traversal Arbitrary File Download — Green CMS 6.5 Medium2026-03-21
CVE-2026-32055 OpenClaw < 2026.2.26 - Workspace Path Boundary Bypass via Non-existent Symlink — OpenClaw 7.6 High2026-03-21
CVE-2026-33238 AVideo has a Path Traversal in listFiles.json.php that Enables Server Filesystem Enumeration — AVideo 4.3 Medium2026-03-20
CVE-2026-3474 EmailKit <= 1.6.3 - Authenticated (Administrator+) Path Traversal via 'emailkit-editor-template' REST API Parameter — EmailKit – Email Customizer for WooCommerce & WP 4.9 Medium2026-03-20
CVE-2026-3339 Keep Backup Daily <= 2.1.1 - Authenticated (Admin+) Limited Path Traversal via 'kbd_path' Parameter — Keep Backup Daily 2.7 Low2026-03-20

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