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-2016-20048 iSelect 1.4.0-2+b1 Local Buffer Overflow via key parameter — iSelect 8.4 High2026-03-28
CVE-2016-20041 Yasr 0.6.9-5 Buffer Overflow via Command-line Parameter — Yasr Screen Reader 8.4 High2026-03-28
CVE-2016-20040 TiEmu 3.03-nogdb+dfsg-3 Buffer Overflow via ROM Parameter — Texas Instrument Emulator 8.4 High2026-03-28
CVE-2026-33989 @mobilenext/mobile-mcp alllows arbitrary file write via Path Traversal in mobile screen capture tools — mobile-mcp 8.1 High2026-03-27
CVE-2026-5027 Langflow - Path Traversal Arbitrary File Write via upload_user_file — langflow 8.8 High2026-03-27
CVE-2026-33748 BuildKit Git URL subdir component can cause access to restricted files — buildkit 7.5 -2026-03-27
CVE-2026-4619 NEC Platforms Aterm Series 安全漏洞 — Aterm WX3600HP 7.5 -2026-03-27
CVE-2026-0394 Open-Xchange OX Dovecot Pro 安全漏洞 — OX Dovecot Pro 5.3 Medium2026-03-27
CVE-2026-33747 BuildKit vulnerable to malicious frontend causing file escape outside of storage root — buildkit 8.4 High2026-03-27
CVE-2026-28786 Open WebUI vulnerable to Path Traversal in `POST /api/v1/audio/transcriptions` — open-webui 4.3 Medium2026-03-26
CVE-2026-33945 Abitrary file write through systemd-creds option — incus 10.0 Critical2026-03-26
CVE-2026-33686 Sharp is Vulnerable to Path Traversal via Unsanitized Extension in FileUtil — sharp 8.8 High2026-03-26
CVE-2026-33670 SiYuan has directory traversal within its publishing service — siyuan 9.8 Critical2026-03-26
CVE-2026-33645 Fireshare has Path Traversal Arbitrary File Write in `/api/uploadChunked` — fireshare 7.1 High2026-03-26
CVE-2026-0964 Libssh: improper sanitation of paths received from scp servers — Red Hat Enterprise Linux 10 8.8 -2026-03-26
CVE-2026-33529 Zoraxy: Authenticated Path Traversal in Config Import leads to RCE — zoraxy 3.3 Low2026-03-26
CVE-2026-33528 GoDoxy has a Path Traversal Vulnerability in its File API — godoxy 6.5 Medium2026-03-26
CVE-2026-32846 OpenClaw Media Parsing Path Traversal to Arbitrary File Read — OpenClaw 8.6 -2026-03-26
CVE-2026-3112 Arbitrary File Read via Advanced Logging Support Packet — Mattermost 6.8 Medium2026-03-26
CVE-2025-41368 Multiple vulnerabilities in Small HTTP server by Smallsrv — Small HTTP 7.8 -2026-03-26
CVE-2026-33183 Saloon has a Fixture Name Path Traversal Vulnerability — saloon 8.1 -2026-03-26
CVE-2026-4758 WP Job Portal <= 2.4.9 - Authenticated (Subscriber+) Arbitrary File Deletion via Resume Custom File Field — WP Job Portal – AI-Powered Recruitment System for Company or Job Board website 8.8 High2026-03-25
CVE-2026-30976 Sonarr Path Traversal vulnerability — Sonarr 8.6 High2026-03-25
CVE-2026-32567 WordPress YML for Yandex Market plugin < 5.3.0 - Arbitrary File Deletion vulnerability — YML for Yandex Market 6.8 Medium2026-03-25
CVE-2026-32522 WordPress WooCommerce Support Ticket System plugin < 18.5 - Arbitrary File Deletion vulnerability — WooCommerce Support Ticket System 8.6 High2026-03-25
CVE-2026-32496 WordPress Spam Protect for Contact Form 7 plugin <= 1.2.9 - Arbitrary File Deletion vulnerability — Spam Protect for Contact Form 7 6.8 Medium2026-03-25
CVE-2026-31913 WordPress Scape theme < 1.5.16 - Arbitrary File Deletion vulnerability — Scape 8.6 High2026-03-25
CVE-2026-27040 WordPress WZone plugin <= 14.0.31 - Arbitrary File Deletion vulnerability — WZone 8.8 High2026-03-25
CVE-2026-25328 WordPress Product File Upload for WooCommerce plugin <= 2.2.4 - Arbitrary File Deletion vulnerability — Product File Upload for WooCommerce 6.8 Medium2026-03-25
CVE-2026-24970 WordPress Energox theme <= 1.2 - Arbitrary File Deletion vulnerability — Energox 7.7 High2026-03-25

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