CWE · MITRE source
CWE-280Improper Handling of Insufficient Permissions or Privileges
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)
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.
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. | |||
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 UPD | 8.8 | 9.8 | 0.2820 | 2024-10-02 |
CVE-2024-29748 KEV UPD | 8.5 | 7.8 | 0.0068 | 2024-04-05 |
CVE-2024-5163 UPD | 7.3 | 9.8 | 0.0051 | 2024-06-17 |
CVE-2025-6573 UPD | 7.3 | 9.8 | 0.0052 | 2025-08-09 |
CVE-2024-25108 UPD | 7.1 | 9.9 | 0.0068 | 2024-02-12 |
CVE-2025-46066 UPD | 6.9 | 9.9 | 0.0035 | 2026-01-12 |
CVE-2019-6570 UPD | 6.8 | 8.8 | 0.0133 | 2019-04-17 |
CVE-2024-22078 UPD | 6.6 | 8.8 | 0.0064 | 2024-03-20 |
CVE-2023-38298 UPD | 6.6 | 8.8 | 0.0045 | 2024-04-22 |
CVE-2024-36451 UPD | 6.6 | 8.8 | 0.0057 | 2024-07-10 |
CVE-2024-6660 UPD | 6.6 | 8.8 | 0.0062 | 2024-07-17 |
CVE-2025-27025 UPD | 6.6 | 8.8 | 0.0063 | 2025-07-02 |
CVE-2025-8109 UPD | 6.6 | 8.8 | 0.0047 | 2025-08-04 |
CVE-2026-40371 UPD | 6.6 | 8.8 | 0.0063 | 2026-06-09 |
CVE-2026-20817 UPD | 6.5 | 7.8 | 0.0542 | 2026-01-13 |
CVE-2024-1608 UPD | 6.4 | 9.1 | 0.0046 | 2024-02-20 |
CVE-2026-24096 | 6.4 | 8.8 | 0.0025 | 2026-04-01 |
CVE-2026-18860 UPD | 6.2 | 8.7 | 0.0044 | 2026-08-11 |
CVE-2023-42931 UPD | 6.1 | 7.8 | 0.0117 | 2024-03-28 |
CVE-2024-46874 | 6.1 | 8.1 | 0.0040 | 2024-12-06 |
CVE-2024-51459 UPD | 6.1 | 8.4 | 0.0014 | 2025-03-19 |
CVE-2025-67848 UPD | 6.1 | 8.1 | 0.0041 | 2026-02-03 |
CVE-2026-0047 UPD | 6.1 | 8.4 | 0.0019 | 2026-03-02 |
CVE-2024-6302 UPD | 6.0 | 8.1 | 0.0028 | 2024-06-25 |
CVE-2024-43702 UPD | 6.0 | 8.1 | 0.0032 | 2024-11-30 |