CWE · MITRE source
CWE-27Path Traversal: 'dir/../../filename'
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize multiple internal "../" 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 'directory/../../filename' manipulation is useful for bypassing some path traversal protection schemes. Sometimes a program only removes one "../" sequence, so multiple "../" can bypass that check. Alternately, this manipulation could be used to bypass a check for "../" at the beginning of the pathname, moving up more than one directory level.
Last updated: 04 July 2026 08:17 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: mostly · 1 mapping(s) from 1 framework(s): ATT&CK 1 (mostly)
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-2024-23897 KEV UPD | 10.0 | 9.8 | 1.0000 | 2024-01-24 |
CVE-2024-24809 UPD | 8.0 | 8.5 | 0.5441 | 2024-04-10 |
CVE-2023-50254 | 7.0 | 9.3 | 0.0212 | 2023-12-22 |
CVE-2024-21896 UPD | 7.0 | 9.8 | 0.0126 | 2024-02-20 |
CVE-2024-27764 UPD | 7.0 | 9.8 | 0.0097 | 2024-03-05 |
CVE-2024-51747 | 7.0 | 9.1 | 0.0082 | 2024-11-11 |
CVE-2026-24457 | 7.0 | 9.1 | 0.0062 | 2026-03-05 |
CVE-2023-34125 | 6.0 | 6.5 | 0.2271 | 2023-07-13 |
CVE-2021-35027 | 5.5 | 7.5 | 0.0198 | 2021-09-29 |
CVE-2022-24785 | 5.5 | 7.5 | 0.0566 | 2022-04-04 |
CVE-2023-27588 | 5.5 | 7.5 | 0.0130 | 2023-03-14 |
CVE-2023-52076 | 5.5 | 8.5 | 0.0102 | 2024-01-25 |
CVE-2024-20348 UPD | 5.5 | 7.5 | 0.0080 | 2024-04-03 |
CVE-2025-58761 | 5.5 | 8.6 | 0.0063 | 2025-09-09 |
CVE-2025-10438 UPD | 5.5 | 8.6 | 0.0041 | 2025-09-25 |
CVE-2025-66518 | 5.5 | 8.8 | 0.0089 | 2026-01-05 |
CVE-2023-20127 | 3.5 | 6.5 | 0.0092 | 2023-04-05 |
CVE-2023-20129 | 3.5 | 6.5 | 0.0092 | 2023-04-05 |
CVE-2023-20130 | 3.5 | 6.5 | 0.0038 | 2023-04-05 |
CVE-2023-20131 | 3.5 | 6.5 | 0.0057 | 2023-04-05 |
CVE-2024-25828 UPD | 3.5 | 4.9 | 0.0061 | 2024-02-22 |
CVE-2024-7458 | 3.5 | 5.5 | 0.0084 | 2024-08-04 |
CVE-2023-20090 | 3.5 | 6.7 | 0.0021 | 2024-11-15 |
CVE-2025-52237 UPD | 3.5 | 6.5 | 0.0047 | 2025-08-05 |
CVE-2026-20018 | 3.5 | 5.9 | 0.0042 | 2026-03-04 |