CWE · MITRE source
CWE-73External Control of File Name or Path
The product allows user input to control or influence paths or file names that are used in filesystem operations.
This could allow an attacker to access or modify system files or other files that are critical to the application. Path manipulation errors occur when the following two conditions are met: For example, the program may give the attacker the ability to overwrite the specified file or run with a configuration controlled by the attacker.
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: mostly · 13 mapping(s) from 4 framework(s): CAPEC 8 (partial) · ATT&CK 3 (partial) · ASVS 5.0 1 (mostly) · OWASP-Web 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A06:2025 Insecure Design.
NIST 800-53 r5 controls that address this weakness (1)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SI-10 | Information Input Validation | SI | Rejects externally supplied file or resource identifiers that fail validity checks. |
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-2020-1631 KEV | 10.0 | 8.8 | 0.0473 | 2020-05-04 |
CVE-2024-43451 KEV | 10.0 | 6.5 | 0.8182 | 2024-11-12 |
CVE-2025-0111 KEV | 10.0 | 6.5 | 0.0186 | 2025-02-12 |
CVE-2025-24054 KEV | 10.0 | 6.5 | 0.5897 | 2025-03-11 |
CVE-2025-33053 KEV UPD | 10.0 | 8.8 | 0.8156 | 2025-06-10 |
CVE-2018-17246 | 8.0 | 9.8 | 0.8225 | 2018-12-20 |
CVE-2021-27250 | 8.0 | 6.5 | 0.6604 | 2021-04-14 |
CVE-2022-39952 | 8.0 | 9.8 | 0.9981 | 2023-02-16 |
CVE-2023-3643 | 8.0 | 7.3 | 0.7521 | 2023-07-12 |
CVE-2023-4634 | 8.0 | 9.8 | 0.8258 | 2023-09-06 |
CVE-2024-8517 | 8.0 | 9.8 | 0.9462 | 2024-09-06 |
CVE-2020-9752 | 7.0 | 9.8 | 0.0115 | 2020-03-23 |
CVE-2018-19945 | 7.0 | 9.1 | 0.0111 | 2020-12-31 |
CVE-2021-38477 | 7.0 | 9.8 | 0.0108 | 2021-10-22 |
CVE-2022-24900 | 7.0 | 9.9 | 0.0804 | 2022-04-29 |
CVE-2023-36019 | 7.0 | 9.6 | 0.1622 | 2023-12-12 |
CVE-2023-47862 | 7.0 | 9.8 | 0.0106 | 2024-01-10 |
CVE-2024-0087 | 7.0 | 9.0 | 0.2008 | 2024-05-14 |
CVE-2024-9142 | 7.0 | 9.8 | 0.0042 | 2024-09-25 |
CVE-2024-5823 | 7.0 | 9.1 | 0.0053 | 2024-10-29 |
CVE-2024-46909 | 7.0 | 9.8 | 0.4917 | 2024-12-02 |
CVE-2024-11838 | 7.0 | 9.8 | 0.0042 | 2024-12-13 |
CVE-2025-0105 | 7.0 | 9.1 | 0.1295 | 2025-01-11 |
CVE-2025-0851 | 7.0 | 9.8 | 0.2308 | 2025-01-29 |
CVE-2024-10834 | 7.0 | 9.1 | 0.0059 | 2025-03-20 |