BaseDraft
CWE-471Modification of Assumed-Immutable Data (MAID)
Category: other
Description
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.
Common consequences· 2
- Integrity — Modify Application DataCommon data types that are attacked are environment variables, web application parameters, and HTTP headers.
- Integrity — Unexpected State
Potential mitigations· 1
- [Architecture and Design, Operation, Implementation]When the data is stored or transmitted through untrusted sources that could modify the data, implement integrity checks to detect unauthorized modification, or store/transmit the data in a trusted location that is free from external influence.
Related CAPEC attack patterns· 5
References
Exploits (incoming)5
| Type | Target | Confidence | Tier |
|---|---|---|---|
| AttackPattern | Application API Button Hijackingcapec-388 | 100% | live |
| AttackPattern | Transaction or Event Tampering via Application API Manipulationcapec-385 | 100% | live |
| AttackPattern | Navigation Remapping To Propagate Malicious Contentcapec-387 | 100% | live |
| AttackPattern | Application API Navigation Remappingcapec-386 | 100% | live |
| AttackPattern | Application API Message Manipulation via Man-in-the-Middlecapec-384 | 100% | live |
(incoming)1
| Type | Target | Confidence | Tier |
|---|---|---|---|
| Vulnerability | CVE-2025-33136cve-2025-33136 | 0% | live |
Related by meaning· 6
Nearest entities by semantic similarity across the cs-graph corpus.