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

Goal: 1000 CNY · Raised: 1325 CNY

100%
Buy Us a Coffee

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

3716 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-4092 Arbitrary File Write via Path Traversal in Google clasp leading to RCE — Clasp 9.8 -2026-03-13
CVE-2025-66249 Apache Livy: Unauthorized directory access — Apache Livy 6.5 -2026-03-13
CVE-2026-23942 SFTP root escape via component-agnostic prefix check in ssh_sftpd — OTP 4.3 -2026-03-13
CVE-2026-22199 Voltronic Power SNMP Web Pro 1.1 Path Traversal via upload.cgi — SNMP Web Pro 7.5 High2026-03-13
CVE-2026-32274 Black: Arbitrary file writes from unsanitized user input in cache file name — black 7.5 -2026-03-12
CVE-2026-32232 ZeptoClaw: Path boundary checks bypass via symlink, TOCTOU, and hardlink — zeptoclaw 6.8AIMediumAI2026-03-12
CVE-2026-32140 Dataease: Redshift JDBC RCE Bypass — dataease 8.0AIHighAI2026-03-12
CVE-2026-32116 Magic Wormhole: "wormhole receive" allows arbitrary local file overwrite — magic-wormhole 9.8AICriticalAI2026-03-12
CVE-2026-28791 Path Traversal in Media Upload Handle in Tina — tinacms 7.4 High2026-03-12
CVE-2026-28793 Path Traversal Leading to Arbitrary File Read, Write and Delete in TinaCMS — cli 8.4 High2026-03-12
CVE-2026-28792 Cross-Origin File Exfiltration via CORS Misconfiguration + Path Traversal in TinaCMS — cli 9.7 Critical2026-03-12
CVE-2026-24125 Path Traversal in @tinacms/graphql — graphql 6.3 Medium2026-03-12
CVE-2026-4044 projectsend Delete import-orphans.php realpath path traversal — projectsend 3.8 Low2026-03-12
CVE-2026-3954 OpenBMB XAgent workspace.py workspace path traversal — XAgent 6.5 Medium2026-03-11
CVE-2019-25480 ARMBot Unrestricted File Upload via upload.php — ARMBot 7.5 High2026-03-11
CVE-2019-25471 FileThingie 2.5.7 Arbitrary File Upload via ft2.php — FileThingie 9.8 Critical2026-03-11
CVE-2026-30234 OpenProject BIM BCF XML Import: <Snapshot> Path Traversal Leads to Arbitrary Local File Read (AFR) — openproject 6.5 Medium2026-03-11
CVE-2026-27897 Vociferous Unauthenticated Remote Path Traversal (RCE via CSRF) — Vociferous 10.0 Critical2026-03-11
CVE-2026-3013 Path Traversal in Coppermine Photo Gallery — Coppermine Photo Gallery 7.5AIHighAI2026-03-11
CVE-2026-32061 OpenClaw < 2026.2.17 - Arbitrary File Read via $include Directive Path Traversal — openclaw 4.4 Medium2026-03-11
CVE-2026-32060 OpenClaw < 2026.2.14 - Path Traversal in apply_patch via Crafted Paths — openclaw 8.8 High2026-03-11
CVE-2026-21360 Adobe Commerce | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') (CWE-22) — Adobe Commerce 6.8 Medium2026-03-11
CVE-2026-28807 Path Traversal in wisp.serve_static allows arbitrary file read — wisp 7.5AIHighAI2026-03-10
CVE-2026-31817 OliveTin's unsafe parsing of UniqueTrackingId can be used to write files — OliveTin 8.5 High2026-03-10
CVE-2026-30952 liquidjs has a path traversal fallback vulnerability — liquidjs 8.1AIHighAI2026-03-10
CVE-2026-27825 MCP Atlassian has an arbitrary file write leading to arbitrary code execution via unconstrained download_path in confluence_download_attachment — mcp-atlassian 9.1 Critical2026-03-10
CVE-2026-30973 Zip Slip arbitrary file write in @appium/support ZIP extraction — support 6.5 Medium2026-03-10
CVE-2026-30958 OneUptime: Path Traversal — Arbitrary File Read (No Auth) — oneuptime 7.2 High2026-03-10
CVE-2025-54659 Fortinet FortiSOAR Agent Communication Bridge 路径遍历漏洞 — FortiSOAR Agent Communication Bridge 5.5 Medium2026-03-10
CVE-2026-30942 Flare has a Path Traversal in /api/avatars/[filename] — Flare 6.5AIMediumAI2026-03-10

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