CWE-676Use of Potentially Dangerous Function

Abstraction: Base · CVEs in our corpus: 11

The product invokes a potentially dangerous function that could introduce a vulnerability if it is used incorrectly, but the function can also be used safely.

Last updated: 14 October 2026 20:41 UTC

OWASP Top 10 for Web (2025)

This weakness contributes to A06:2025 Insecure Design.

Control responseHuman-reviewed

Answering this weakness across the control lifecycle, from our framework cross-walks.

Prevent

Stop it (NIST 800-53 / CSF Protect)

PR.PS-06
SA-11 Developer Testing and Evaluation
SA-8 Security and Privacy Engineering Principles
SA-15 Development Process, Standards, and Tools

Detect

Catch it (CSF Detect / Respond)

—

Harden

Shrink the surface (DISA STIG)

—

Validate

Prove the fix (OWASP ASVS)

—

NIST 800-53 r5 controls PROPOSED for this weakness (0)AI-assisted

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.

Top CVEs of this weakness type, ranked by Risk Priority

CVE	Risk	CVSS	EPSS	Published
`CVE-2021-27474`	7.6	10.0	0.0161	2022-03-23
`CVE-2022-39063`	6.1	7.5	0.0120	2022-09-16
`CVE-2026-54499`	5.7	7.5	0.0052	2026-07-08
`CVE-2025-65117`	5.2	7.4	0.0022	2026-01-16
`CVE-2024-38434`	5.1	6.5	0.0044	2024-07-21
`CVE-2026-48696`	4.7	6.2	0.0018	2026-05-26
`CVE-2024-50307`	4.4	5.5	0.0028	2024-10-28
`CVE-2025-67604`	4.3	5.3	0.0042	2026-05-12
`CVE-2026-14501`	3.7	4.3	0.0046	2026-07-17
`CVE-2025-14601`	3.5	0.0	0.0106	2026-08-20
`CVE-2024-37387`	3.3	4.0	0.0016	2024-06-19