CWE · MITRE source
CWE-114Process Control
Executing commands or loading libraries from an untrusted source or in an untrusted environment can cause an application to execute malicious commands (and payloads) on behalf of an attacker.
Process control vulnerabilities of the first type occur when either data enters the application from an untrusted source and the data is used as part of a string representing a command that is executed by the application. By executing the command, the application gives an attacker a privilege or capability that the attacker would not otherwise have.
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: full · 19 mapping(s) from 9 framework(s): ATT&CK 8 (mostly) · STIG oracle linux 8 3 (mostly) · CAPEC 2 (partial) · OWASP-Web 1 (full) · STIG windows 10 1 (partial) · STIG windows 11 1 (partial) · STIG windows server 2016 1 (partial) · STIG windows server 2019 1 (partial) · STIG windows server 2022 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-2022-23748 KEV | 10.0 | 7.8 | 0.0909 | 2022-11-17 |
CVE-2024-56346 | 7.0 | 10.0 | 0.0106 | 2025-03-18 |
CVE-2024-56347 | 7.0 | 9.6 | 0.0086 | 2025-03-18 |
CVE-2025-1950 UPD | 7.0 | 9.3 | 0.0019 | 2025-04-22 |
CVE-2025-36250 | 7.0 | 10.0 | 0.0063 | 2025-11-13 |
CVE-2025-36251 | 7.0 | 9.6 | 0.0051 | 2025-11-13 |
CVE-2019-8461 | 5.5 | 7.8 | 0.0112 | 2019-08-29 |
CVE-2020-11075 | 5.5 | 7.7 | 0.0184 | 2020-05-27 |
CVE-2020-6024 | 5.5 | 7.8 | 0.0027 | 2021-01-20 |
CVE-2020-8107 | 5.5 | 8.2 | 0.0032 | 2022-02-18 |
CVE-2023-4487 | 5.5 | 7.8 | 0.0018 | 2023-09-05 |
CVE-2023-40299 | 5.5 | 7.8 | 0.0035 | 2023-10-04 |
CVE-2024-25021 UPD | 5.5 | 8.4 | 0.0027 | 2024-02-22 |
CVE-2024-32004 | 5.5 | 8.1 | 0.0127 | 2024-05-14 |
CVE-2025-23385 | 5.5 | 7.8 | 0.0013 | 2025-01-28 |
CVE-2025-0160 | 5.5 | 8.1 | 0.0049 | 2025-02-28 |
CVE-2026-29046 | 5.5 | 8.2 | 0.0039 | 2026-03-06 |
CVE-2019-8453 | 3.5 | 5.5 | 0.0032 | 2019-04-17 |
CVE-2019-8458 | 3.5 | 4.4 | 0.0097 | 2019-06-20 |
CVE-2020-11081 | 3.5 | 5.3 | 0.0059 | 2020-07-10 |
CVE-2020-6014 | 3.5 | 6.5 | 0.0037 | 2020-11-02 |
CVE-2021-25736 | 3.5 | 5.8 | 0.0091 | 2023-10-30 |
CVE-2024-8207 | 3.5 | 6.4 | 0.0020 | 2024-08-27 |
CVE-2024-44168 | 3.5 | 5.5 | 0.0025 | 2024-09-17 |
CVE-2026-26945 | 3.5 | 5.3 | 0.0018 | 2026-03-18 |