CWE · MITRE source
CWE-472External Control of Assumed-Immutable Web Parameter
The web application does not sufficiently verify inputs that are assumed to be immutable but are actually externally controllable, such as hidden form fields.
If a web product does not properly protect assumed-immutable values from modification in hidden form fields, parameters, cookies, or URLs, this can lead to modification of critical data. Web applications often mistakenly make the assumption that data passed to the client in hidden fields or cookies is not susceptible to tampering. Improper validation of data that are user-controllable can lead to the application processing incorrect, and often malicious, input. For example, custom cookies commonly store session data or persistent data across sessions. This kind of session data is normally involved in security related decisions on the server side, such as user authentication and access control. Thus, the cookies might contain sensitive data such as user credentials and privileges. This is a dangerous practice, as it can often lead to improper reliance on the value of the client-provided cookie by the server side application.
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 · 6 mapping(s) from 3 framework(s): CAPEC 4 (partial) · OWASP-Web 1 (mostly) · ATT&CK 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 (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-2025-35939 KEV UPD | 10.0 | 5.3 | 0.0112 | 2025-05-07 |
CVE-2021-1289 | 7.0 | 9.8 | 0.0424 | 2021-02-04 |
CVE-2021-1290 | 7.0 | 9.8 | 0.0424 | 2021-02-04 |
CVE-2021-1291 | 7.0 | 9.8 | 0.0424 | 2021-02-04 |
CVE-2021-1292 | 7.0 | 9.8 | 0.0418 | 2021-02-04 |
CVE-2021-1293 | 7.0 | 9.8 | 0.0542 | 2021-02-04 |
CVE-2021-1294 | 7.0 | 9.8 | 0.0418 | 2021-02-04 |
CVE-2021-1295 | 7.0 | 9.8 | 0.0424 | 2021-02-04 |
CVE-2024-25153 UPD | 7.0 | 9.8 | 0.4174 | 2024-03-13 |
CVE-2025-43930 UPD | 7.0 | 9.8 | 0.0046 | 2025-07-07 |
CVE-2025-43933 UPD | 7.0 | 9.8 | 0.0037 | 2025-07-07 |
CVE-2026-34751 | 7.0 | 9.1 | 0.0031 | 2026-04-01 |
CVE-2026-11088 UPD | 7.0 | 9.6 | 0.0032 | 2026-06-04 |
CVE-2026-13796 | 7.0 | 9.6 | 0.0029 | 2026-06-30 |
CVE-2026-14387 | 7.0 | 9.6 | 0.0028 | 2026-07-01 |
CVE-2017-5260 | 5.5 | 8.8 | 0.0813 | 2017-12-20 |
CVE-2017-5261 | 5.5 | 8.8 | 0.0889 | 2017-12-20 |
CVE-2024-9123 | 5.5 | 8.8 | 0.0036 | 2024-09-25 |
CVE-2024-7025 | 5.5 | 8.8 | 0.0059 | 2024-11-27 |
CVE-2025-22384 | 5.5 | 7.5 | 0.0040 | 2025-01-04 |
CVE-2025-0436 | 5.5 | 8.8 | 0.0040 | 2025-01-15 |
CVE-2025-25382 | 5.5 | 7.5 | 0.0030 | 2025-03-10 |
CVE-2025-30236 | 5.5 | 8.6 | 0.0034 | 2025-03-19 |
CVE-2025-3530 UPD | 5.5 | 7.5 | 0.0045 | 2025-04-23 |
CVE-2025-47245 UPD | 5.5 | 8.1 | 0.0042 | 2025-05-04 |