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: 04 July 2026 08:17 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 · 3 mapping(s) from 3 framework(s): CAPEC 1 (mostly) · OWASP-Web 1 (mostly) · 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 (1)AI
| 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. |
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-21985 KEV | 10.0 | 9.8 | 1.0000 | 2021-05-26 |
CVE-2022-30287 | 8.0 | 8.0 | 0.7028 | 2022-07-28 |
CVE-2024-0200 | 8.0 | 7.2 | 0.7173 | 2024-01-16 |
CVE-2024-4990 | 8.0 | 9.1 | 0.7939 | 2025-03-20 |
CVE-2018-1000613 | 7.0 | 9.8 | 0.0477 | 2018-07-09 |
CVE-2019-1003040 | 7.0 | 9.8 | 0.0337 | 2019-03-28 |
CVE-2019-1003041 | 7.0 | 9.8 | 0.0337 | 2019-03-28 |
CVE-2021-31522 | 7.0 | 9.8 | 0.0290 | 2022-01-06 |
CVE-2023-32217 | 7.0 | 9.0 | 0.0063 | 2023-06-05 |
CVE-2023-6943 | 7.0 | 9.8 | 0.0184 | 2024-01-30 |
CVE-2024-8015 | 7.0 | 9.1 | 0.0082 | 2024-10-09 |
CVE-2025-53693 UPD | 7.0 | 9.8 | 0.1378 | 2025-09-03 |
CVE-2025-63690 | 7.0 | 9.1 | 0.0086 | 2025-11-07 |
CVE-2025-34393 | 7.0 | 9.8 | 0.0059 | 2025-12-10 |
CVE-2026-42027 UPD | 7.0 | 9.8 | 0.0069 | 2026-05-04 |
CVE-2018-5511 | 6.0 | 7.2 | 0.1476 | 2018-04-13 |
CVE-2025-3600 UPD | 6.0 | 7.5 | 0.1906 | 2025-05-14 |
CVE-2017-7536 | 5.5 | 7.0 | 0.0048 | 2018-01-10 |
CVE-2019-3834 | 5.5 | 7.3 | 0.0101 | 2019-10-03 |
CVE-2019-10174 | 5.5 | 8.8 | 0.0309 | 2019-11-25 |
CVE-2020-7857 | 5.5 | 7.5 | 0.0101 | 2021-04-20 |
CVE-2021-32647 | 5.5 | 8.0 | 0.0285 | 2021-06-01 |
CVE-2022-26469 | 5.5 | 7.8 | 0.0016 | 2022-09-06 |
CVE-2022-41853 | 5.5 | 8.0 | 0.0352 | 2022-10-06 |
CVE-2023-34102 | 5.5 | 8.3 | 0.0161 | 2023-06-05 |