CWE · MITRE source
CWE-281Improper Preservation of Permissions
The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended.
Last updated: 04 July 2026 14:16 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 · 7 mapping(s) from 4 framework(s): ATT&CK 3 (partial) · STIG windows server 2022 2 (partial) · STIG windows server 2019 1 (mostly) · OWASP-Web 1 (mostly)
OWASP Top 10 for Web (2025)
This weakness contributes to A01:2025 Broken Access Control.
NIST 800-53 r5 controls that address this weakness (1)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
PS-5 | Personnel Transfer | PS | Forces removal or modification of permissions no longer required after reassignment, preventing improper preservation of old access rights. |
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-2017-8543 KEV | 10.0 | 9.8 | 0.7376 | 2017-06-15 |
CVE-2019-0233 | 8.0 | 7.5 | 0.6876 | 2020-09-14 |
CVE-2017-8589 | 7.0 | 9.8 | 0.2616 | 2017-07-11 |
CVE-2018-4115 | 7.0 | 9.8 | 0.0230 | 2018-04-03 |
CVE-2020-10083 | 7.0 | 9.1 | 0.0108 | 2020-03-13 |
CVE-2020-18890 | 7.0 | 9.8 | 0.0152 | 2021-05-06 |
CVE-2021-29971 | 7.0 | 9.8 | 0.0102 | 2021-08-05 |
CVE-2023-28668 | 7.0 | 9.8 | 0.0083 | 2023-04-02 |
CVE-2021-33990 | 7.0 | 9.8 | 0.1192 | 2023-04-16 |
CVE-2020-36070 | 7.0 | 9.8 | 0.0108 | 2023-04-26 |
CVE-2023-34034 | 7.0 | 9.1 | 0.0347 | 2023-07-19 |
CVE-2023-48240 | 7.0 | 9.0 | 0.0071 | 2023-11-20 |
CVE-2023-47463 | 7.0 | 9.8 | 0.0128 | 2023-11-30 |
CVE-2024-36532 | 7.0 | 10.0 | 0.0045 | 2024-06-21 |
CVE-2024-41644 | 7.0 | 9.8 | 0.0068 | 2024-12-06 |
CVE-2024-41645 | 7.0 | 9.8 | 0.0068 | 2024-12-06 |
CVE-2024-41646 | 7.0 | 9.8 | 0.0068 | 2024-12-06 |
CVE-2024-41648 | 7.0 | 9.8 | 0.0047 | 2024-12-06 |
CVE-2024-41649 | 7.0 | 9.8 | 0.0068 | 2024-12-06 |
CVE-2024-41650 | 7.0 | 9.8 | 0.0047 | 2024-12-06 |
CVE-2024-54465 | 7.0 | 9.8 | 0.0086 | 2024-12-12 |
CVE-2024-55507 | 7.0 | 9.8 | 0.0059 | 2025-01-03 |
CVE-2024-46622 | 7.0 | 9.8 | 0.0057 | 2025-01-06 |
CVE-2024-54879 | 7.0 | 9.1 | 0.0091 | 2025-01-06 |
CVE-2024-54880 | 7.0 | 9.1 | 0.0087 | 2025-01-06 |