CWE · MITRE source
CWE-95Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. "eval").
Last updated: 20 November 2026 15:29 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 · 27 mapping(s) from 5 framework(s): ATT&CK 18 (full) · ISO_IEC_27002_2022 4 (mostly) · 800-53 3 (mostly) · ASVS 5.0 1 (full) · 1 (mostly)
OWASP Top 10 for Web (2025)
This weakness contributes to A05:2025 Injection.
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-2023-46731 UPD | 10.0 | 10.0 | 0.8970 | 2023-11-06 |
CVE-2024-21650 UPD | 10.0 | 10.0 | 0.9348 | 2024-01-08 |
CVE-2023-26477 UPD | 9.9 | 10.0 | 0.7476 | 2023-03-02 |
CVE-2024-36401 KEV UPD | 9.9 | 9.8 | 0.9981 | 2024-07-01 |
CVE-2024-36404 UPD | 9.9 | 9.8 | 0.7607 | 2024-07-02 |
CVE-2024-7954 UPD | 9.9 | 9.8 | 0.9005 | 2024-08-23 |
CVE-2025-24893 KEV UPD | 9.9 | 9.8 | 0.9997 | 2025-02-20 |
CVE-2026-33017 KEV UPD | 9.9 | 9.8 | 0.9681 | 2026-03-20 |
CVE-2026-61511 UPD | 9.9 | 9.8 | 0.7427 | 2026-07-27 |
CVE-2023-37462 UPD | 9.6 | 9.9 | 0.9159 | 2023-07-14 |
CVE-2022-36099 UPD | 9.5 | 9.9 | 0.7635 | 2022-09-08 |
CVE-2022-36100 UPD | 9.5 | 9.9 | 0.7361 | 2022-09-08 |
CVE-2023-29509 UPD | 9.5 | 9.9 | 0.7618 | 2023-04-16 |
CVE-2023-35150 UPD | 9.5 | 9.9 | 0.7765 | 2023-06-23 |
CVE-2023-50721 UPD | 9.5 | 9.9 | 0.7881 | 2023-12-15 |
CVE-2024-31465 UPD | 9.5 | 9.9 | 0.7558 | 2024-04-10 |
CVE-2024-31984 UPD | 9.5 | 9.9 | 0.8300 | 2024-04-10 |
CVE-2026-0769 UPD | 9.1 | 9.8 | 0.4115 | 2026-01-23 |
CVE-2024-31982 UPD | 9.0 | 10.0 | 0.3452 | 2024-04-10 |
CVE-2023-7101 KEV UPD | 8.5 | 7.8 | 0.1896 | 2023-12-24 |
CVE-2025-54322 UPD | 8.5 | 10.0 | 0.1527 | 2025-12-27 |
CVE-2026-1470 UPD | 8.2 | 9.9 | 0.2040 | 2026-01-27 |
CVE-2024-31996 UPD | 7.8 | 10.0 | 0.0210 | 2024-04-10 |
CVE-2013-10051 UPD | 7.8 | 9.8 | 0.0367 | 2025-08-01 |
CVE-2022-36010 UPD | 7.7 | 10.0 | 0.0153 | 2022-08-15 |