CWE · MITRE source
CWE-913Improper Control of Dynamically-Managed Code Resources
The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements.
Many languages offer powerful features that allow the programmer to dynamically create or modify existing code, or resources used by code such as variables and objects. While these features can offer significant flexibility and reduce development time, they can be extremely dangerous if attackers can directly influence these code resources in unexpected ways.
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 · 9 mapping(s) from 3 framework(s): ATT&CK 7 (mostly) · STIG windows 10 1 (partial) · STIG windows 11 1 (partial)
NIST 800-53 r5 controls that address this weakness (1)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-18 | Mobile Code | SC | Requiring explicit authorization and ongoing control of mobile code implements proper management of dynamically loaded code resources. |
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-2025-68613 KEV | 10.0 | 9.9 | 0.9788 | 2025-12-19 |
CVE-2023-29017 | 8.0 | 10.0 | 0.6319 | 2023-04-06 |
CVE-2023-43177 | 8.0 | 9.8 | 0.8180 | 2023-11-18 |
CVE-2023-50386 | 8.0 | 8.8 | 0.8384 | 2024-02-09 |
CVE-2006-7079 | 7.0 | 9.8 | 0.1285 | 2007-03-02 |
CVE-2014-9852 | 7.0 | 9.8 | 0.0293 | 2017-03-17 |
CVE-2017-3202 | 7.0 | 9.8 | 0.0821 | 2018-06-11 |
CVE-2020-15568 | 7.0 | 9.8 | 0.2849 | 2021-01-30 |
CVE-2021-32563 | 7.0 | 9.8 | 0.0308 | 2021-05-11 |
CVE-2021-22387 | 7.0 | 9.8 | 0.0095 | 2021-08-02 |
CVE-2022-36067 | 7.0 | 10.0 | 0.4787 | 2022-09-06 |
CVE-2022-44000 | 7.0 | 9.8 | 0.0095 | 2022-11-16 |
CVE-2023-29199 | 7.0 | 9.8 | 0.0385 | 2023-04-14 |
CVE-2023-33175 | 7.0 | 9.1 | 0.0065 | 2023-05-30 |
CVE-2023-4041 | 7.0 | 9.8 | 0.0033 | 2023-08-23 |
CVE-2024-5452 | 7.0 | 9.8 | 0.2649 | 2024-06-06 |
CVE-2024-8953 | 7.0 | 9.8 | 0.0110 | 2025-03-20 |
CVE-2025-6384 UPD | 7.0 | 9.1 | 0.0085 | 2025-06-19 |
CVE-2025-25270 UPD | 7.0 | 9.8 | 0.0063 | 2025-07-08 |
CVE-2025-66398 | 7.0 | 9.6 | 0.1793 | 2026-01-01 |
CVE-2026-22709 | 7.0 | 9.8 | 0.0122 | 2026-01-26 |
CVE-2026-23830 | 7.0 | 10.0 | 0.0112 | 2026-01-28 |
CVE-2026-25049 | 7.0 | 9.9 | 0.0120 | 2026-02-04 |
CVE-2026-33286 | 7.0 | 9.1 | 0.0063 | 2026-03-24 |
CVE-2026-34156 | 7.0 | 9.9 | 0.3650 | 2026-03-31 |