CWE · MITRE source
CWE-23Relative Path Traversal
The 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.
Last updated: 20 November 2026 11:24 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: full · 39 mapping(s) from 6 framework(s): ATT&CK 20 (mostly) · ISO_IEC_27002_2022 6 (mostly) · MSP_OFFERINGS 6 (partial) · 800-53 5 (mostly) · ASVS 5.0 1 (full) · 1 (mostly)
OWASP Top 10 for Web (2025)
This weakness contributes to A01:2025 Broken Access Control.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (0)
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| 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).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2021-40870 KEV UPD | 9.9 | 9.8 | 0.9302 | 2021-09-13 |
CVE-2025-64446 KEV UPD | 9.9 | 9.8 | 0.9108 | 2025-11-14 |
CVE-2026-76519 KEV | 9.9 | 9.8 | 0.0623 | 2026-10-14 |
CVE-2023-34990 UPD | 8.7 | 9.8 | 0.2504 | 2024-12-18 |
CVE-2020-5410 KEV UPD | 8.5 | 7.5 | 0.9559 | 2020-06-02 |
CVE-2026-41948 UPD | 8.4 | 9.4 | 0.2271 | 2026-05-18 |
CVE-2024-27199 KEV UPD | 8.3 | 7.3 | 0.9999 | 2024-03-04 |
CVE-2020-8271 UPD | 8.2 | 9.8 | 0.1079 | 2020-11-16 |
CVE-2024-24578 UPD | 8.2 | 10.0 | 0.0874 | 2024-03-18 |
CVE-2025-34510 UPD | 8.0 | 8.8 | 0.2647 | 2025-06-17 |
CVE-2020-10619 UPD | 7.9 | 9.1 | 0.1433 | 2020-04-09 |
CVE-2020-17518 UPD | 7.9 | 7.5 | 0.4939 | 2021-01-05 |
CVE-2022-23854 UPD | 7.9 | 7.5 | 0.4969 | 2022-12-23 |
CVE-2012-6069 UPD | 7.8 | 10.0 | 0.0264 | 2013-01-21 |
CVE-2020-12006 UPD | 7.8 | 9.8 | 0.0369 | 2020-05-08 |
CVE-2020-27304 UPD | 7.8 | 9.8 | 0.0327 | 2021-10-21 |
CVE-2024-2053 UPD | 7.8 | 7.5 | 0.4458 | 2024-03-21 |
CVE-2025-55752 UPD | 7.8 | 7.5 | 0.5426 | 2025-10-27 |
CVE-2017-9664 UPD | 7.7 | 9.8 | 0.0254 | 2018-05-24 |
CVE-2019-17640 UPD | 7.7 | 9.8 | 0.0200 | 2020-10-15 |
CVE-2020-25172 UPD | 7.7 | 9.8 | 0.0203 | 2020-11-06 |
CVE-2020-5405 UPD | 7.6 | 6.5 | 0.6854 | 2020-03-05 |
CVE-2020-10631 UPD | 7.6 | 9.8 | 0.0148 | 2020-04-09 |
CVE-2022-28814 UPD | 7.6 | 9.8 | 0.0132 | 2022-09-28 |
CVE-2022-39345 UPD | 7.6 | 9.8 | 0.0177 | 2022-10-25 |