CWE · MITRE source
CWE-25Path 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. Sometimes a program checks for "../" at the beginning of the input, so a "/../" can bypass that check.
Last updated: 04 July 2026 11:13 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-2022-20775 KEV | 10.0 | 7.8 | 0.1247 | 2022-09-30 |
CVE-2025-68916 | 7.0 | 9.1 | 0.0225 | 2025-12-24 |
CVE-2022-20818 | 5.5 | 7.8 | 0.0059 | 2022-09-30 |
CVE-2023-6118 | 5.5 | 7.5 | 0.0076 | 2023-11-23 |
CVE-2023-52076 | 5.5 | 8.5 | 0.0102 | 2024-01-25 |
CVE-2023-6919 | 5.5 | 7.5 | 0.0058 | 2024-01-26 |
CVE-2023-52138 | 5.5 | 8.2 | 0.0165 | 2024-02-05 |
CVE-2024-2442 UPD | 5.5 | 7.5 | 0.0070 | 2024-03-19 |
CVE-2023-6947 | 5.5 | 7.7 | 0.0073 | 2024-12-10 |
CVE-2025-0225 | 3.5 | 4.3 | 0.0046 | 2025-01-05 |
CVE-2026-23877 | 3.5 | 4.3 | 0.0051 | 2026-01-19 |
CVE-2025-58286 | 1.5 | 3.3 | 0.0010 | 2025-10-11 |