CWE · MITRE source
CWE-749Exposed Dangerous Method or Function
The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted.
This weakness can lead to a wide variety of resultant weaknesses, depending on the behavior of the exposed method. It can apply to any number of technologies and approaches, such as ActiveX controls, Java functions, IOCTLs, and so on. The exposure can occur in a few different 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: full · 8 mapping(s) from 6 framework(s): STIG ubuntu 22 04 3 (mostly) · OWASP-Web 1 (full) · ASVS 5.0 1 (mostly) · ATT&CK 1 (mostly) · CAPEC 1 (partial) · STIG ubuntu 24 04 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A01:2025 Broken Access Control.
NIST 800-53 r5 controls that address this weakness (2)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
CM-7 | Least Functionality | CM | Explicitly prohibiting dangerous or unnecessary functions and services prevents exposure of methods that could be directly exploited. |
SC-25 | Thin Nodes | SC | Minimal functionality removes or avoids exposure of dangerous methods and functions. |
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-2006-1547 KEV | 10.0 | 7.5 | 0.5464 | 2006-03-30 |
CVE-2010-0738 KEV | 10.0 | 5.3 | 0.7942 | 2010-04-28 |
CVE-2010-1428 KEV | 10.0 | 7.5 | 0.6231 | 2010-04-28 |
CVE-2018-19322 KEV | 10.0 | 7.8 | 0.0187 | 2018-12-21 |
CVE-2018-10931 | 8.0 | 9.8 | 0.6786 | 2018-08-09 |
CVE-2021-34996 | 8.0 | 8.8 | 0.8226 | 2022-01-13 |
CVE-2023-38124 | 8.0 | 8.8 | 0.5582 | 2024-05-03 |
CVE-2014-5415 | 7.0 | 9.1 | 0.0434 | 2016-10-05 |
CVE-2019-18342 | 7.0 | 9.9 | 0.0213 | 2019-12-12 |
CVE-2020-15623 | 7.0 | 9.8 | 0.0833 | 2020-07-28 |
CVE-2020-8212 | 7.0 | 9.8 | 0.0164 | 2020-08-17 |
CVE-2020-2503 | 7.0 | 9.0 | 0.0078 | 2020-12-24 |
CVE-2021-28809 | 7.0 | 9.8 | 0.1580 | 2021-07-08 |
CVE-2021-42128 | 7.0 | 9.8 | 0.0450 | 2021-12-07 |
CVE-2022-4136 | 7.0 | 9.8 | 0.0094 | 2022-11-24 |
CVE-2023-40150 | 7.0 | 9.8 | 0.0101 | 2023-09-11 |
CVE-2023-3656 | 7.0 | 9.8 | 0.0099 | 2023-10-03 |
CVE-2023-40151 | 7.0 | 10.0 | 0.0115 | 2023-11-21 |
CVE-2023-39226 | 7.0 | 9.8 | 0.0118 | 2023-11-30 |
CVE-2023-49583 | 7.0 | 9.1 | 0.0109 | 2023-12-12 |
CVE-2023-50422 | 7.0 | 9.1 | 0.0135 | 2023-12-12 |
CVE-2023-50423 | 7.0 | 9.1 | 0.0111 | 2023-12-12 |
CVE-2023-50424 | 7.0 | 9.1 | 0.0113 | 2023-12-12 |
CVE-2023-5389 | 7.0 | 9.1 | 0.0078 | 2024-01-30 |
CVE-2024-25675 UPD | 7.0 | 9.8 | 0.0082 | 2024-02-09 |