CWE · MITRE source
CWE-470Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code.
If the product uses external inputs to determine which class to instantiate or which method to invoke, then an attacker could supply values to select unexpected classes or methods. If this occurs, then the attacker could create control flow paths that were not intended by the developer. These paths could bypass authentication or access control checks, or otherwise cause the product to behave in an unexpected manner. This situation becomes a doomsday scenario if the attacker can upload files into a location that appears on the product's classpath (CWE-427) or add new entries to the product's classpath (CWE-426). Under either of these conditions, the attacker can use reflection to introduce new, malicious behavior into the product.
Last updated: 22 August 2026 00:25 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 · 1 mapping(s) from 1 framework(s): CAPEC 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 that address this weakness (1)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-44 | Detonation Chambers | SC | Externally controlled class or code selection can be resolved and invoked inside the chamber, surfacing unsafe reflection without system impact. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2021-21985 KEV UPD | 9.9 | 9.8 | 1.0000 | 2021-05-26 |
CVE-2024-4990 UPD | 9.4 | 9.1 | 0.8008 | 2025-03-20 |
CVE-2022-30287 UPD | 8.6 | 8.0 | 0.7065 | 2022-07-28 |
CVE-2025-53693 UPD | 8.3 | 9.8 | 0.1412 | 2025-09-03 |
CVE-2018-1000613 UPD | 7.9 | 9.8 | 0.0477 | 2018-07-09 |
CVE-2019-1003040 UPD | 7.8 | 9.8 | 0.0337 | 2019-03-28 |
CVE-2019-1003041 UPD | 7.8 | 9.8 | 0.0337 | 2019-03-28 |
CVE-2021-31522 UPD | 7.8 | 9.8 | 0.0290 | 2022-01-06 |
CVE-2024-0200 UPD | 7.8 | 7.2 | 0.7173 | 2024-01-16 |
CVE-2023-6943 UPD | 7.7 | 9.8 | 0.0213 | 2024-01-30 |
CVE-2026-44416 UPD | 7.5 | 9.8 | 0.0116 | 2026-08-10 |
CVE-2025-34393 UPD | 7.4 | 9.8 | 0.0069 | 2025-12-10 |
CVE-2026-42027 UPD | 7.4 | 9.8 | 0.0067 | 2026-05-04 |
CVE-2026-46562 | 7.4 | 9.8 | 0.0078 | 2026-07-16 |
CVE-2026-40008 | 7.3 | 9.8 | 0.0042 | 2026-07-10 |
CVE-2025-3600 UPD | 7.2 | 7.5 | 0.2414 | 2025-05-14 |
CVE-2019-10174 UPD | 7.0 | 8.8 | 0.0309 | 2019-11-25 |
CVE-2023-33652 UPD | 7.0 | 8.8 | 0.0249 | 2023-06-06 |
CVE-2024-28121 UPD | 6.9 | 8.8 | 0.0155 | 2024-03-12 |
CVE-2022-4993 | 6.9 | 9.1 | 0.0048 | 2026-08-13 |
CVE-2026-13051 | 6.9 | 9.1 | 0.0045 | 2026-08-13 |
CVE-2024-6096 UPD | 6.7 | 8.8 | 0.0086 | 2024-07-24 |
CVE-2026-65608 | 6.7 | 8.8 | 0.0085 | 2026-07-23 |
CVE-2023-34102 UPD | 6.6 | 8.3 | 0.0161 | 2023-06-05 |
CVE-2024-8014 UPD | 6.6 | 8.8 | 0.0062 | 2024-10-09 |