CWE · MITRE source
CWE-24Path Traversal: '../filedir'
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "../" sequences that can resolve to a location that is outside of that directory.
This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory. The "../" manipulation is the canonical manipulation for operating systems that use "/" as directory separators, such as UNIX- and Linux-based systems. In some cases, it is useful for bypassing protection schemes in environments for which "/" is supported but not the primary separator, such as Windows, which uses "\" but can also accept "/".
Last updated: 04 July 2026 00:28 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: partial · 2 mapping(s) from 1 framework(s): ATT&CK 2 (partial)
NIST 800-53 r5 controls that address this weakness (0)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
| No NIST controls proposed yet. | |||
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing). Drafted by Grok and spot-checked by Claude Opus 4.8.
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2025-27920 KEV UPD | 10.0 | 7.2 | 0.0181 | 2025-05-05 |
CVE-2022-38129 | 7.0 | 9.8 | 0.1838 | 2022-08-10 |
CVE-2023-6699 | 7.0 | 9.1 | 0.0087 | 2024-01-11 |
CVE-2025-61318 | 7.0 | 9.1 | 0.0061 | 2025-12-08 |
CVE-2026-39813 | 7.0 | 9.8 | 0.1674 | 2026-04-14 |
CVE-2025-60344 | 6.0 | 8.6 | 0.1027 | 2025-10-21 |
CVE-2021-26725 | 5.5 | 7.2 | 0.0106 | 2021-02-22 |
CVE-2020-7882 | 5.5 | 7.5 | 0.0121 | 2021-11-22 |
CVE-2021-33036 | 5.5 | 8.8 | 0.0325 | 2022-06-15 |
CVE-2022-36065 | 5.5 | 7.5 | 0.0106 | 2022-09-06 |
CVE-2023-1800 | 5.5 | 7.3 | 0.0352 | 2023-04-02 |
CVE-2023-52076 | 5.5 | 8.5 | 0.0102 | 2024-01-25 |
CVE-2024-22079 UPD | 5.5 | 7.5 | 0.0102 | 2024-03-20 |
CVE-2024-23657 | 5.5 | 8.8 | 0.0114 | 2024-08-05 |
CVE-2025-48050 UPD | 5.5 | 7.5 | 0.0039 | 2025-05-15 |
CVE-2025-53513 UPD | 5.5 | 8.8 | 0.0065 | 2025-07-08 |
CVE-2025-54769 UPD | 5.5 | 8.8 | 0.0304 | 2025-07-29 |
CVE-2025-59049 | 5.5 | 7.5 | 0.0166 | 2025-09-10 |
CVE-2025-57618 | 5.5 | 7.3 | 0.0065 | 2025-10-14 |
CVE-2023-53691 | 5.5 | 8.3 | 0.0117 | 2025-10-22 |
CVE-2025-63298 | 5.5 | 8.2 | 0.0047 | 2025-10-30 |
CVE-2025-51661 | 5.5 | 7.5 | 0.0046 | 2025-11-19 |
CVE-2025-67364 | 5.5 | 7.5 | 0.0058 | 2026-01-07 |
CVE-2026-28427 | 5.5 | 7.5 | 0.0043 | 2026-03-04 |
CVE-2026-41082 UPD | 5.5 | 7.3 | 0.0018 | 2026-04-16 |