CWE · MITRE source
CWE-471Modification of Assumed-Immutable Data (MAID)
The product does not properly protect an assumed-immutable element from being modified by an attacker.
This occurs when a particular input is critical enough to the functioning of the application that it should not be modifiable at all, but it is. Certain resources are often assumed to be immutable when they are not, such as hidden form fields in web applications, cookies, and reverse DNS lookups.
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 · 10 mapping(s) from 3 framework(s): CAPEC 5 (partial) · ATT&CK 4 (mostly) · STIG windows 10 1 (mostly)
NIST 800-53 r5 controls that address this weakness (1)AI
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-33 | Transmission Preparation Integrity | SC | Checksums and integrity protection during transformation/packing detect unauthorized modification of data assumed to be immutable before it is transmitted. |
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-2020-8147 | 7.0 | 9.8 | 0.0315 | 2020-04-03 |
CVE-2020-8158 | 7.0 | 9.8 | 0.0212 | 2020-09-18 |
CVE-2022-25893 | 7.0 | 9.8 | 0.0143 | 2022-12-21 |
CVE-2022-21824 | 6.0 | 8.2 | 0.2151 | 2022-02-24 |
CVE-2018-3728 | 5.5 | 8.8 | 0.0423 | 2018-03-30 |
CVE-2018-3719 | 5.5 | 8.8 | 0.0212 | 2018-06-07 |
CVE-2018-3720 | 5.5 | 8.8 | 0.0202 | 2018-06-07 |
CVE-2018-3722 | 5.5 | 8.8 | 0.0204 | 2018-06-07 |
CVE-2018-3723 | 5.5 | 8.8 | 0.0204 | 2018-06-07 |
CVE-2020-8116 | 5.5 | 7.3 | 0.0308 | 2020-02-04 |
CVE-2020-15256 | 5.5 | 7.7 | 0.0153 | 2020-10-19 |
CVE-2020-8268 | 5.5 | 7.5 | 0.0128 | 2020-11-09 |
CVE-2020-26245 | 5.5 | 8.1 | 0.0192 | 2020-11-27 |
CVE-2023-2904 | 5.5 | 7.3 | 0.0056 | 2023-06-07 |
CVE-2024-55551 | 5.5 | 8.3 | 0.0058 | 2025-03-19 |
CVE-2024-9876 UPD | 5.5 | 7.3 | 0.0023 | 2025-04-30 |
CVE-2025-33136 UPD | 5.5 | 7.1 | 0.0029 | 2025-05-22 |
CVE-2026-44798 UPD | 5.5 | 7.1 | 0.0028 | 2026-05-28 |
CVE-2018-3721 | 3.5 | 6.5 | 0.0241 | 2018-06-07 |
CVE-2020-26237 | 3.5 | 5.8 | 0.0130 | 2020-11-24 |
CVE-2020-26268 | 3.5 | 4.4 | 0.0020 | 2020-12-10 |
CVE-2021-37177 | 3.5 | 6.5 | 0.0037 | 2021-09-14 |
CVE-2021-37193 | 3.5 | 4.3 | 0.0035 | 2021-09-14 |
CVE-2021-42701 | 3.5 | 5.0 | 0.0057 | 2021-11-05 |
CVE-2021-24046 | 3.5 | 5.3 | 0.0070 | 2022-01-14 |