CWE · MITRE source
CWE-602Client-Side Enforcement of Server-Side Security
The product is composed of a server that relies on the client to implement a mechanism that is intended to protect the server.
When the server relies on protection mechanisms placed on the client side, an attacker can modify the client-side behavior to bypass the protection mechanisms, resulting in potentially unexpected interactions between the client and server. The consequences will vary, depending on what the mechanisms are trying to protect.
Last updated: 04 July 2026 08:17 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: full · 18 mapping(s) from 4 framework(s): CAPEC 11 (partial) · ASVS 5.0 5 (full) · OWASP-Web 1 (full) · 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-2020-24683 | 7.0 | 9.8 | 0.0141 | 2020-12-22 |
CVE-2022-20658 | 7.0 | 9.6 | 0.0139 | 2022-01-14 |
CVE-2022-1525 | 7.0 | 9.1 | 0.0067 | 2022-09-06 |
CVE-2023-0750 | 7.0 | 9.8 | 0.0045 | 2023-04-06 |
CVE-2024-12603 | 7.0 | 9.8 | 0.0053 | 2024-12-13 |
CVE-2025-27681 | 7.0 | 9.8 | 0.0070 | 2025-03-05 |
CVE-2025-32469 UPD | 7.0 | 9.9 | 0.0117 | 2025-05-13 |
CVE-2025-33024 UPD | 7.0 | 9.9 | 0.0117 | 2025-05-13 |
CVE-2025-33025 UPD | 7.0 | 9.9 | 0.0117 | 2025-05-13 |
CVE-2025-10640 | 7.0 | 9.8 | 0.0089 | 2025-10-21 |
CVE-2025-51682 | 7.0 | 9.8 | 0.0040 | 2025-12-01 |
CVE-2026-23478 | 7.0 | 9.8 | 0.0040 | 2026-01-13 |
CVE-2026-30783 | 7.0 | 9.8 | 0.0038 | 2026-03-05 |
CVE-2026-13901 | 7.0 | 9.6 | 0.0034 | 2026-06-30 |
CVE-2026-14109 | 7.0 | 9.6 | 0.0025 | 2026-06-30 |
CVE-2017-12161 | 5.5 | 8.8 | 0.0133 | 2018-02-21 |
CVE-2020-8162 | 5.5 | 7.5 | 0.0307 | 2020-06-19 |
CVE-2021-21531 | 5.5 | 8.1 | 0.0069 | 2021-04-30 |
CVE-2022-3308 | 5.5 | 7.4 | 0.0060 | 2022-11-01 |
CVE-2024-28029 UPD | 5.5 | 8.8 | 0.0065 | 2024-03-21 |
CVE-2024-31491 | 5.5 | 8.8 | 0.0083 | 2024-05-14 |
CVE-2024-42340 | 5.5 | 8.3 | 0.0032 | 2024-08-25 |
CVE-2024-44106 | 5.5 | 8.8 | 0.0024 | 2024-09-10 |
CVE-2024-23666 | 5.5 | 7.5 | 0.0274 | 2024-11-12 |
CVE-2024-52008 | 5.5 | 8.8 | 0.0054 | 2024-11-26 |