Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1336 CNY

100%

CWE-472 (对假设不可变Web参数的外部可控制) — Vulnerability Class 136

136 vulnerabilities classified as CWE-472 (对假设不可变Web参数的外部可控制). AI Chinese analysis included.

CWE-472 represents a logic flaw where web applications incorrectly assume certain input parameters are immutable, such as hidden form fields, cookies, or URL arguments, despite being fully controllable by external users. Attackers typically exploit this weakness by manipulating these trusted values to bypass authorization checks, alter business logic, or escalate privileges, effectively tricking the server into processing unauthorized actions. To mitigate this risk, developers must avoid relying on client-side data for security-critical decisions. Instead, they should enforce server-side validation for all inputs, ensuring that any parameter influencing application state is rigorously verified against expected values. By treating all user-supplied data as untrusted, regardless of its origin or apparent immutability, developers can prevent attackers from subverting application logic through simple parameter tampering.

MITRE CWE Description
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.
Common Consequences (1)
IntegrityModify Application Data
Without appropriate protection mechanisms, the client can easily tamper with cookies and similar web data. Reliance on the cookies without detailed validation can lead to problems such as SQL injection. If you use cookie values for security related decisions on the server side, manipulating the cook…
Mitigations (2)
ImplementationAssume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range…
ImplementationInputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174). Such errors could be used to bypass allowlist validation schemes by introducing dangerous inputs after they have been checked.
Examples (2)
In this example, a web application uses the value of a hidden form field (accountID) without having done any input validation because it was assumed to be immutable.
String accountID = request.getParameter("accountID"); User user = getUserFromID(Long.parseLong(accountID));
Bad · Java
Hidden fields should not be trusted as secure parameters.
<input type="hidden"
Bad · HTML
CVE IDTitleCVSSSeverityPublished
CVE-2026-1982 Persian Elementor (المنتور فارسی) <= 2.8.1 - Unauthenticated Price Manipulation via ZarinPal Widget — المنتور فارسی 5.3 Medium2026-07-30
CVE-2026-7484 Improper Access Control in Abis Technology's AVESİS — AVESİS 5.3 Medium2026-07-24
CVE-2026-65052 Ninja Forms Calculation and Payment Total Tampering via Fail-Open get_calc_value in ListSelect and ListRadio Fields — Ninja Forms 7.5 High2026-07-21
CVE-2026-56877 Skillable SCORM Lab Launch Integration 输入验证错误漏洞 — SCORM Lab Launch Integration 6.3 Medium2026-07-13
CVE-2026-59817 Ghost: Paid gift memberships obtainable at minimal cost via the donations feature — Ghost 5.3 Medium2026-07-09
CVE-2026-14389 Google Chrome 输入验证错误漏洞 — Chrome--2026-07-01
CVE-2026-14430 Google Chrome 输入验证错误漏洞 — Chrome--2026-07-01
CVE-2026-14387 Google Chrome 输入验证错误漏洞 — Chrome--2026-07-01
CVE-2026-14391 Google Chrome 输入验证错误漏洞 — Chrome--2026-07-01
CVE-2026-14069 Google Chrome 输入验证错误漏洞 — Chrome--2026-06-30
CVE-2026-13974 Google Chrome 输入验证错误漏洞 — Chrome--2026-06-30
CVE-2026-13938 Google Chrome 输入验证错误漏洞 — Chrome--2026-06-30
CVE-2026-13841 Google Chrome 输入验证错误漏洞 — Chrome--2026-06-30
CVE-2026-13801 Google Chrome 输入验证错误漏洞 — Chrome--2026-06-30
CVE-2026-13796 Google Chrome 输入验证错误漏洞 — Chrome--2026-06-30
CVE-2026-13281 Google Chrome 输入验证错误漏洞 — Chrome--2026-06-25
CVE-2026-42655 WordPress Best Payments Plugin for WP plugin <= 4.6.19 - Payment Bypass vulnerability — Best Payments Plugin for WP 7.5 Medium2026-06-15
CVE-2025-59382 QTS, QuTS hero, QuTScloud, QVP (QVR Pro appliances) — QTS--2026-06-10
CVE-2026-11678 Google Chrome 安全漏洞 — Chrome--2026-06-08
CVE-2026-11669 Google Chrome 安全漏洞 — Chrome--2026-06-08
CVE-2026-11655 Google Chrome 安全漏洞 — Chrome--2026-06-08
CVE-2026-11640 Google Chrome 安全漏洞 — Chrome--2026-06-08
CVE-2026-11290 Google Chrome 安全漏洞 — Chrome--2026-06-04
CVE-2026-11281 Google Chrome 安全漏洞 — Chrome--2026-06-04
CVE-2026-11211 Google Chrome 安全漏洞 — Chrome--2026-06-04
CVE-2026-11171 Google Chrome 安全漏洞 — Chrome--2026-06-04
CVE-2026-11088 Google Chrome 安全漏洞 — Chrome--2026-06-04
CVE-2026-11085 Google Chrome 安全漏洞 — Chrome--2026-06-04
CVE-2026-11058 Google Chrome 安全漏洞 — Chrome--2026-06-04
CVE-2026-11044 Google Chrome 安全漏洞 — Chrome--2026-06-04

Vulnerabilities classified as CWE-472 (对假设不可变Web参数的外部可控制) represent 136 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.