CWE · MITRE source
CWE-286Incorrect User Management
The product does not properly manage a user within its environment.
Users can be assigned to the wrong group (class) of permissions resulting in unintended access rights to sensitive objects.
Last updated: 04 July 2026 11:13 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 · 13 mapping(s) from 4 framework(s): ATT&CK 10 (mostly) · STIG oracle linux 9 1 (partial) · STIG rhel 9 1 (partial) · OWASP-Web 1 (partial)
OWASP Top 10 for Web (2025)
This weakness contributes to A06:2025 Insecure Design.
NIST 800-53 r5 controls that address this weakness (2)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
IA-4 | Identifier Management | IA | Directly implements correct management of identifiers for individuals, groups, roles, services, and devices. |
PS-5 | Personnel Transfer | PS | Requires confirmation and adjustment of user access rights during personnel transfers, mitigating incorrect user management. |
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-2023-26689 | 7.0 | 9.8 | 0.0062 | 2024-09-25 |
CVE-2024-48853 UPD | 7.0 | 9.0 | 0.0034 | 2025-05-22 |
CVE-2025-7972 UPD | 7.0 | 9.1 | 0.0048 | 2025-08-14 |
CVE-2025-64725 | 7.0 | 9.8 | 0.0032 | 2025-12-15 |
CVE-2021-21553 | 5.5 | 7.3 | 0.0022 | 2021-08-03 |
CVE-2023-3932 | 5.5 | 8.2 | 0.0088 | 2023-08-03 |
CVE-2023-25519 | 5.5 | 7.8 | 0.0015 | 2023-09-12 |
CVE-2023-20253 | 5.5 | 7.1 | 0.0017 | 2023-09-27 |
CVE-2022-35503 | 5.5 | 7.5 | 0.0054 | 2024-04-22 |
CVE-2024-28020 | 5.5 | 8.0 | 0.0037 | 2024-06-11 |
CVE-2024-9312 | 5.5 | 7.5 | 0.0028 | 2024-10-10 |
CVE-2024-58105 | 5.5 | 7.3 | 0.0015 | 2025-03-25 |
CVE-2025-59943 | 5.5 | 8.1 | 0.0039 | 2025-10-03 |
CVE-2026-35638 | 5.5 | 8.8 | 0.0029 | 2026-04-09 |
CVE-2021-26262 | 3.5 | 5.5 | 0.0063 | 2021-11-19 |
CVE-2022-32260 | 3.5 | 6.5 | 0.0072 | 2022-06-14 |
CVE-2022-45857 | 3.5 | 6.5 | 0.0031 | 2023-01-05 |
CVE-2023-0857 | 3.5 | 5.9 | 0.0061 | 2023-05-11 |
CVE-2023-3115 | 3.5 | 5.4 | 0.0035 | 2023-09-29 |
CVE-2023-3914 | 3.5 | 5.4 | 0.0037 | 2023-09-29 |
CVE-2023-3907 | 3.5 | 4.9 | 0.0059 | 2023-12-17 |
CVE-2023-51750 | 3.5 | 4.6 | 0.0029 | 2024-01-11 |
CVE-2024-29296 UPD | 3.5 | 5.3 | 0.0130 | 2024-04-10 |
CVE-2024-27269 | 3.5 | 6.8 | 0.0043 | 2024-05-14 |
CVE-2024-52359 | 3.5 | 4.3 | 0.0030 | 2024-11-19 |