CWE-807: Reliance on Untrusted Inputs in a Security Decision
112 CVEs have CWE-807 as their primary weakness. 2 of them are in the CISA KEV catalog. The highest EPSS score among them is 70.823%.
The product uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses the protection mechanism.
Without sufficient encryption, integrity checking, or other mechanism, any input that originates from an outsider cannot be trusted.
Child of CWE-693: Protection Mechanism Failure
Mitigations
- Architecture and Design: Store state information and sensitive data on the server side only. Ensure that the system definitively and unambiguously keeps track of its own state and user state and has rules defined for legitimate state transitions. Do not allow any application user to affect state directly in any way other than through legitimate actions leading to state transitions. If information must be stored on the client, do not do so without encryption and integrity checking, or otherwise having a mechanism on the server side to catch tampering. Use a message authentication code (MAC) algorithm, such as Hash Message Authentication Code (HMAC) [REF-529]. Apply this against the state or sensitive data that has to be exposed, which can guarantee the integrity of the data - i.e., that the data has not been modified. Ensure that a strong hash function is used (CWE-328).
- Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. With a stateless protocol such as HTTP, use a framework that maintains the state for you. Examples include ASP.NET View State [REF-756] and the OWASP ESAPI Session Management feature [REF-45]. Be careful of language features that provide state support, since these might be provided as a convenience to the programmer and may not be considering security.
- Architecture and Design: For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Operation Implementation: When using PHP, configure the application so that it does not use register_globals. During implementation, develop the application so that it does not rely on this feature, but be wary of implementing a register_globals emulation that is subject to weaknesses such as CWE-95, CWE-621, and similar issues.
- Architecture and Design Implementation: Understand all the potential areas where untrusted inputs can enter your software: parameters or arguments, cookies, anything read from the network, environment variables, reverse DNS lookups, query results, request headers, URL components, e-mail, files, filenames, databases, and any external systems that provide data to the application. Remember that such inputs may be obtained indirectly through API calls. Identify all inputs that are used for security decisions and determine if you can modify the design so that you do not have to rely on submitted inputs at all. For example, you may be able to keep critical information about the user's session on the server side instead of recording it within external data.
Observed examples
- CVE-2009-1549: Attacker can bypass authentication by setting a cookie to a specific value.
- CVE-2009-1619: Attacker can bypass authentication and gain admin privileges by setting an admin cookie to 1.
- CVE-2009-0864: Content management system allows admin privileges by setting a login cookie to OK.
- CVE-2008-5784: e-dating application allows admin privileges by setting the admin cookie to 1.
- CVE-2008-6291: Web-based email list manager allows attackers to gain admin privileges by setting a login cookie to admin.
Top released CVEs
KEV first, then the highest EPSS score, the highest CVSS score and the newest.
| CVE | Published | Severity | CVSS | EPSS | Description |
|---|---|---|---|---|---|
| CVE-2026-21509 | 2026-01-26 | HIGH | 7.8 | 70.823% | Reliance on untrusted inputs in a security decision in Microsoft Office allows an unauthorized attacker to bypass a security feature locally. |
| CVE-2026-21514 | 2026-02-10 | HIGH | 7.8 | 1.587% | Reliance on untrusted inputs in a security decision in Microsoft Office Word allows an unauthorized attacker to bypass a security feature locally. |
| CVE-2026-130070 | 2026-11-16 | CRITICAL | 9.1 | not scored | Ghost by muneeb141 on the main branch from commit c731cdf through commit 672dfec contains an authentication bypass vulnerability in the whitelisted… |
| CVE-2026-129869 | 2026-11-16 | MEDIUM | 5.3 | not scored | SamWaf 1.0.128 through 1.3.25-beta.11 contains a request body inspection bypass vulnerability in WafEngine.ServeHTTP that skips bodies with chunked encoding or… |
| CVE-2026-115219 | 2026-11-17 | LOW | 3.8 | not scored | GitLab has remediated an issue in GitLab EE affecting all versions from 19.2 before 19.3.9, 19.4 before 19.4.8, and 19.5 before 19.5.6 that under certain… |
| CVE-2026-129885 | 2026-11-16 | LOW | 3.7 | not scored | Unrolled Secure before 1.18.0 contains an SSLRedirect bypass vulnerability in Secure.isSSL() that trusts the client-supplied r.URL.Scheme to determine HTTPS… |
Get more CVE data from the API.
curl 'https://api.contrastcyber.com/cwe_lookup/CWE-807'curl 'https://api.contrastcyber.com/cve_search?cwe_id=CWE-807'
Sources
- Vulnerability data from the National Vulnerability Database (NIST) and the CVE Program. CVE records: Copyright © 1999-2026, The MITRE Corporation, used under the CVE Program Terms of Use. CVE® is a registered trademark of The MITRE Corporation.
- CWE definitions: Copyright © 2006-2026, The MITRE Corporation, used under the CWE Terms of Use. CWE is a trademark of The MITRE Corporation.
- EPSS scores by FIRST.org EPSS, used with attribution.
- KEV catalog and SSVC decisions by CISA.
- Advisory data from the GitHub Advisory Database through OSV.dev (CC BY 4.0).
- Exploit metadata from the Exploit Database (GPL-2.0-only, metadata only).
- Nuclei template names from nuclei-templates (MIT).