CWE · MITRE source
CWE-99Improper Control of Resource Identifiers ('Resource Injection')
The product receives input from an upstream component, but it does not restrict or incorrectly restricts the input before it is used as an identifier for a resource that may be outside the intended sphere of control.
A resource injection issue occurs when the following two conditions are met: This may enable an attacker to access or modify otherwise protected system resources.
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: partial · 7 mapping(s) from 4 framework(s): ASVS 5.0 4 (partial) · CAPEC 1 (partial) · OWASP-Web 1 (partial) · ATT&CK 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A05:2025 Injection.
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-2017-5159 | 7.0 | 9.8 | 0.0243 | 2017-02-13 |
CVE-2024-57971 | 7.0 | 9.1 | 0.0067 | 2025-02-16 |
CVE-2025-0756 UPD | 7.0 | 9.1 | 0.0079 | 2025-04-16 |
CVE-2025-2410 UPD | 7.0 | 9.1 | 0.0043 | 2025-05-22 |
CVE-2025-43491 | 7.0 | 9.8 | 0.0026 | 2025-09-09 |
CVE-2019-6545 | 6.0 | 7.5 | 0.1386 | 2019-02-13 |
CVE-2020-5230 | 5.5 | 7.7 | 0.0117 | 2020-01-30 |
CVE-2020-8177 | 5.5 | 7.8 | 0.0124 | 2020-12-14 |
CVE-2021-22879 | 5.5 | 8.8 | 0.0470 | 2021-04-14 |
CVE-2021-42360 | 5.5 | 7.6 | 0.0059 | 2021-11-17 |
CVE-2022-39369 | 5.5 | 8.0 | 0.0106 | 2022-11-01 |
CVE-2023-3517 | 5.5 | 8.5 | 0.0064 | 2023-12-12 |
CVE-2023-6605 | 5.5 | 7.2 | 0.0027 | 2025-01-06 |
CVE-2024-5706 | 5.5 | 8.8 | 0.0066 | 2025-02-19 |
CVE-2026-3693 | 5.5 | 7.3 | 0.0040 | 2026-03-08 |
CVE-2016-8615 | 3.5 | 5.3 | 0.0450 | 2018-08-01 |
CVE-2019-1860 | 3.5 | 5.9 | 0.0126 | 2019-05-16 |
CVE-2020-6245 | 3.5 | 6.7 | 0.0034 | 2020-05-12 |
CVE-2022-1287 | 3.5 | 6.5 | 0.0071 | 2022-04-09 |
CVE-2022-27670 | 3.5 | 6.5 | 0.0091 | 2022-04-12 |
CVE-2022-3774 | 3.5 | 5.4 | 0.0113 | 2022-10-31 |
CVE-2023-2980 | 3.5 | 6.3 | 0.0112 | 2023-05-30 |
CVE-2024-4294 | 3.5 | 6.3 | 0.0086 | 2024-04-27 |
CVE-2024-4817 | 3.5 | 6.3 | 0.0092 | 2024-05-14 |
CVE-2024-7437 | 3.5 | 5.4 | 0.0044 | 2024-08-03 |