Security Resilience

CWE · MITRE source

CWE-648Incorrect Use of Privileged APIs

Abstraction: Base · CVEs in our corpus: 68

The product does not conform to the API requirements for a function call that requires extra privileges. This could allow attackers to gain privileges by causing the function to be called incorrectly.

When a product contains certain functions that perform operations requiring an elevated level of privilege, the caller of a privileged API must be careful to: If the caller of the API does not follow these requirements, then it may allow a malicious user or process to elevate their privilege, hijack the process, or steal sensitive data. For instance, it is important to know if privileged APIs do not shed their privileges before returning to the caller or if the privileged function might make certain assumptions about the data, context or state information passed to it by the caller. It is important to always know when and how privileged APIs can be called in order to ensure that their elevated level of privilege cannot be exploited.

Last updated: 15 October 2026 14:21 UTC

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
  • AC-3 Access Enforcement
  • SA-11 Developer Testing and Evaluation
  • SA-8 Security and Privacy Engineering Principles
Detect
Catch it (CSF Detect / Respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V3.5.2
  • V6.4.6

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-2026-76460 KEV 10.010.00.14032026-09-16
CVE-2019-14813 8.29.80.10962019-09-06
CVE-2024-8785 8.29.80.09662024-12-02
CVE-2019-1010178 7.99.80.04592019-07-24
CVE-2022-2023 7.89.80.03202022-06-20
CVE-2024-11068 7.59.80.01172024-11-11
CVE-2026-20122 KEV 7.55.40.25482026-02-25
CVE-2023-4972 7.49.80.00692023-09-14
CVE-2019-14869 7.18.80.03432019-11-15
CVE-2025-54769 7.18.80.03332025-07-29
CVE-2026-413297.09.90.00522026-04-21
CVE-2026-413866.99.10.00572026-04-28
CVE-2024-37018 6.89.10.00432024-05-31
CVE-2023-28062 6.78.80.00772023-04-11
CVE-2026-356396.78.80.00842026-04-09
CVE-2023-29507 6.69.10.00902023-04-16
CVE-2025-7344 6.68.80.00562025-07-21
CVE-2026-356636.68.80.00522026-04-10
CVE-2026-356696.68.80.00522026-04-10
CVE-2025-5997 6.58.80.00372025-07-28
CVE-2026-20126 6.58.80.00312026-02-25
CVE-2026-637276.58.80.00442026-07-28
CVE-2019-14811 6.47.80.03752019-09-03
CVE-2026-41225 6.49.10.00462026-05-13
CVE-2019-10216 6.37.80.02302019-11-27