CWE · MITRE source
CWE-842Placement of User into Incorrect Group
The product or the administrator places a user into an incorrect group.
If the incorrect group has more access or privileges than the intended group, the user might be able to bypass intended security policy to access unexpected resources or perform unexpected actions. The access-control system might not be able to detect malicious usage of this group membership.
Last updated: 04 July 2026 00:28 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 · 8 mapping(s) from 6 framework(s): STIG windows server 2016 2 (mostly) · STIG windows server 2019 2 (mostly) · STIG windows 10 1 (mostly) · STIG windows 11 1 (mostly) · STIG windows server 2022 1 (mostly) · ATT&CK 1 (partial)
NIST 800-53 r5 controls that address this weakness (0)AI
| 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). 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-2022-31007 | 6.0 | 4.9 | 0.2610 | 2022-05-31 |
CVE-2022-2989 | 5.5 | 7.1 | 0.0031 | 2022-09-13 |
CVE-2022-2990 | 5.5 | 7.1 | 0.0033 | 2022-09-13 |
CVE-2022-3650 | 5.5 | 7.8 | 0.0033 | 2023-01-17 |
CVE-2023-25575 | 5.5 | 7.7 | 0.0060 | 2023-02-28 |
CVE-2024-25632 | 5.5 | 8.6 | 0.0039 | 2024-10-01 |
CVE-2024-10082 | 5.5 | 8.7 | 0.0047 | 2024-11-06 |
CVE-2022-45097 | 3.5 | 6.3 | 0.0041 | 2023-02-01 |