Security Resilience

CWE · MITRE source

CWE-280Improper Handling of Insufficient Permissions or Privileges

Abstraction: Base · CVEs in our corpus: 183

The product does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. This may cause it to follow unexpected code paths that may leave the product in an invalid state.

Last updated: 19 November 2026 21:43 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 · 17 mapping(s) from 7 framework(s): ISO_IEC_27002_2022 5 (mostly) · 3 (mostly) · 800-53 3 (partial) · STIG rhel 9 2 (partial) · STIG oracle linux 8 2 (partial) · STIG oracle linux 9 1 (partial) · ATT&CK 1 (partial)

See the full cumulative-coverage rollup →

OWASP Top 10 for Web (2025)

This weakness contributes to A10:2025 Mishandling of Exceptional Conditions.

Control responseHuman-reviewed

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

Prevent
Stop it (NIST 800-53 / CSF Protect)
  • PR.AA-05
  • PR.PS-04
  • AC-3 Access Enforcement
  • AC-24 Access Control Decisions
Detect
Catch it (CSF Detect / Respond)
  • DE.CM-09
Harden
Shrink the surface (DISA STIG)
  • 6 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.2.2
  • V8.3.3
Our mappings

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

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.
Our mappings

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).

Direction: ← other covers this; → this covers other (F/M/P = full / mostly / partial). gov = governs / implements (a mandate, not coverage).

Top CVEs of this weakness type, ranked by Risk Priority

CVE Risk CVSS EPSS Published
CVE-2024-24116 8.89.80.28202024-10-02
CVE-2024-29748 KEV 8.57.80.00682024-04-05
CVE-2024-5163 7.39.80.00512024-06-17
CVE-2025-6573 7.39.80.00522025-08-09
CVE-2024-25108 7.19.90.00682024-02-12
CVE-2025-46066 6.99.90.00352026-01-12
CVE-2019-6570 6.88.80.01332019-04-17
CVE-2024-22078 6.68.80.00642024-03-20
CVE-2023-38298 6.68.80.00452024-04-22
CVE-2024-36451 6.68.80.00572024-07-10
CVE-2024-6660 6.68.80.00622024-07-17
CVE-2025-27025 6.68.80.00632025-07-02
CVE-2025-8109 6.68.80.00472025-08-04
CVE-2026-40371 6.68.80.00632026-06-09
CVE-2026-20817 6.57.80.05422026-01-13
CVE-2024-1608 6.49.10.00462024-02-20
CVE-2026-240966.48.80.00252026-04-01
CVE-2026-18860 6.28.70.00442026-08-11
CVE-2023-42931 6.17.80.01172024-03-28
CVE-2024-468746.18.10.00402024-12-06
CVE-2024-51459 6.18.40.00142025-03-19
CVE-2025-67848 6.18.10.00412026-02-03
CVE-2026-0047 6.18.40.00192026-03-02
CVE-2024-6302 6.08.10.00282024-06-25
CVE-2024-43702 6.08.10.00322024-11-30