CWE · MITRE source
CWE-641Improper Restriction of Names for Files and Other Resources
The product constructs the name of a file or other resource using input from an upstream component, but it does not restrict or incorrectly restricts the resulting name.
This may produce resultant weaknesses. For instance, if the names of these resources contain scripting characters, it is possible that a script may get executed in the client's browser if the application ever displays the name of the resource on a dynamically generated web page. Alternately, if the resources are consumed by some application parser, a specially crafted name can exploit some vulnerability internal to the parser, potentially resulting in execution of arbitrary code on the server machine. The problems will vary based on the context of usage of such malformed resource names and whether vulnerabilities are present in or assumptions are made by the targeted technology that would make code execution possible.
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: partial · 1 mapping(s) from 1 framework(s): ATT&CK 1 (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-2021-41146 | 5.5 | 8.8 | 0.0145 | 2021-10-21 |
CVE-2022-36302 | 5.5 | 8.8 | 0.0051 | 2022-08-01 |
CVE-2023-0046 | 5.5 | 7.2 | 0.0102 | 2023-01-04 |
CVE-2025-21361 | 5.5 | 7.8 | 0.0073 | 2025-01-14 |
CVE-2025-21402 | 5.5 | 7.8 | 0.0065 | 2025-01-14 |
CVE-2025-47173 UPD | 5.5 | 7.8 | 0.0054 | 2025-06-10 |
CVE-2025-47953 UPD | 5.5 | 8.4 | 0.0046 | 2025-06-10 |
CVE-2026-25177 | 5.5 | 8.8 | 0.0124 | 2026-03-10 |
CVE-2026-27140 UPD | 5.5 | 8.8 | 0.0066 | 2026-04-08 |
CVE-2026-50023 | 5.5 | 8.3 | 0.0056 | 2026-06-23 |
CVE-2022-23536 | 3.5 | 6.5 | 0.0075 | 2022-12-19 |
CVE-2024-30063 | 3.5 | 6.7 | 0.0102 | 2024-06-11 |
CVE-2024-45312 | 3.5 | 5.3 | 0.0048 | 2024-09-02 |
CVE-2024-47260 | 3.5 | 6.5 | 0.0037 | 2025-03-04 |
CVE-2019-25623 | 3.5 | 6.2 | 0.0019 | 2026-03-23 |