CWE-23: Relative Path Traversal
low-riskThe product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory.
Abstraction: Base
Common Consequences
Integrity
→
Execute Unauthorized Code or Commands
Integrity
→
Modify Files or Directories
Confidentiality
→
Read Files or Directories
Availability
→
DoS: Crash, Exit, or Restart
Detection Methods
Automated Static Analysis
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)
Real-World Examples (10)
| CVE | CVSS | EPSS | KEV |
|---|---|---|---|
| CVE-2020-5410 | 7.5 | 94.4% | Y |
| CVE-2021-40870 | 9.8 | 94.3% | Y |
| CVE-2020-17518 | 7.5 | 93.8% | — |
| CVE-2025-64446 | 9.8 | 93.1% | Y |
| CVE-2022-23854 | 7.5 | 92.2% | — |
| CVE-2023-2356 | 7.5 | 89.9% | — |
| CVE-2020-5405 | 6.5 | 88.0% | — |
| CVE-2025-34510 | 8.8 | 86.0% | — |
| CVE-2024-27199 | 7.3 | 82.5% | — |
| CVE-2020-5284 | 4.4 | 82.0% | — |
9
/ 100
low-risk
Active Threat
9/50 · Minimal
Exploit Availability
0/50 · Minimal