Security weakness
CWE-602 Client-Side Enforcement of Server-Side Security
A class-level weakness that can lead to downtime and lost sales and accounts and admin areas exposed. Here is what it is, what it can cost you and how to close it.
- Senior security engineers
- 540+ projects delivered
- Reply within one business day
Quick answer
What is CWE-602?
Client-Side Enforcement of Server-Side Security: The product includes a server that relies on the client to implement a protection mechanism that is intended to protect the server.
Business impact
What CWE-602 could cost your business
MITRE documents what this weakness can do. Here is what that means for a website, store or app.
Availability
Downtime and lost sales
Crashes, slowdowns or exhausted resources can take your site, store or app offline.
- DoS: Crash, Exit, or Restart
Access Control
Accounts and admin areas exposed
Logins and permission checks can be bypassed, putting admin and customer accounts at risk.
- Bypass Protection Mechanism
- Gain Privileges or Assume Identity
Free security check
Is CWE-602 hiding in your site?
A senior engineer checks your site, store or app for this weakness and the rest of the CWE Top 25, then sends a prioritized fix plan within one business day. No obligation.
Official definition
How MITRE defines CWE-602
Client-Side Enforcement of Server-Side Security
The product includes a server that relies on the client to implement a protection mechanism that is intended to protect the server.
Prevention
How to fix CWE-602, phase by phase
Every mitigation from the CWE entry, in the order a project runs: plan, build, test, operate.
- 01
Architecture and Design
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side. 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. Even though client-side.
- If some degree of trust is required between the two entities, then use integrity checking and strong authentication to ensure that the inputs are coming from a trusted source. Design the product so that this trust is managed in a centralized fashion, especially if there are complex or numerous communication channels, in order to reduce the risks that the implementer will.
Detection and evidence
How CWE-602 is found, and where it has hit
The testing methods MITRE recommends, and real vulnerabilities this weakness has caused.
How it is detected
- FuzzingUse dynamic tools and techniques that interact with the software using large test suites with many diverse inputs, such as fuzz testing (fuzzing), robustness testing, and fault injection. The software’s operation may slow down, but it should not become unstable, crash, or generate incorrect results.
- Manual AnalysisUse tools and techniques that require manual (human) analysis, such as penetration testing, threat modeling, and interactive tools that allow the tester to record and modify an active session. These may be more effective than strictly automated techniques. This is especially the case with weaknesses.
Real vulnerabilities it caused
- CVE-2024-50653Chain: e-commerce product has a "front-end restriction" for coupon use (CWE-602), but the server does not restrict the number of requests for the same coupon (CWE-799)
- CVE-2022-33139SCADA system only uses client-side authentication, allowing adversaries to impersonate other users.
- CVE-2006-6994Chain: ASP program allows upload of .asp files (CWE-434) by bypassing client-side checks (CWE-601.
- CVE-2007-0163steganography products embed password information in the carrier file, which can be extracted from a modified client.
- CVE-2007-0164steganography products embed password information in the carrier file, which can be extracted from a modified client.
- CVE-2007-0100client allows server to modify client’s configuration and overwrite arbitrary files.
How we fix it
From finding to fixed: how Codefreex closes CWE-602
Scan and confirm
We test your site, store or app for this weakness and the rest of the CWE Top 25 with automated scanning and manual review, and confirm what is actually exploitable.
Fix at the source
We change the code, configuration or dependency that causes it, not just the symptom, and plan the changes to avoid downtime.
Verify the fix
We retest every finding, check that nothing else broke and hand you a short report you can share with your team, client or auditor.
Keep it fixed
Updates, monitoring and maintenance so the weakness does not return with the next plugin, theme, app or code change.
Website SecurityPenetration TestingMalware Removal & Hack RepairWordPress Maintenance
Related weaknesses
Weaknesses related to CWE-602
FAQ
CWE-602: FAQs
Short answers for owners and developers. Not sure whether your site is affected? Ask us to check.
What is CWE-602?
CWE-602, “Client-Side Enforcement of Server-Side Security”, is a software weakness catalogued by MITRE in the Common Weakness Enumeration. The product includes a server that relies on the client to implement a protection mechanism that is intended to protect the server.
How serious is CWE-602?
MITRE rates the likelihood of exploit as Medium. It can affect availability, access control, with impacts such as dos: crash, exit, or restart, bypass protection mechanism, gain privileges or assume identity. The real risk depends on where the weakness sits and what data or functions it exposes.
How do you prevent CWE-602?
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove. If some degree of trust is required between the two entities, then use integrity checking and strong authentication to ensure that the inputs are coming from a trusted source. Design the product so.
Can Codefreex check my site for CWE-602?
Yes. A senior engineer reviews your site, store or app for CWE-602 and the rest of the CWE Top 25, confirms what is exploitable and sends a prioritized fix plan within one business day. Start with the free security check form on this page.
Which technologies does CWE-602 affect?
MITRE lists it as applicable to ICS/OT, Mobile. In practice any software that matches the weakness description can be affected, including custom code, plugins, themes and third-party libraries.
Free security check
Find out if CWE-602 affects your site
Send your URL. A senior engineer checks for this weakness and the rest of the CWE Top 25, and replies within one business day with what to fix first.
- A senior strategist reviews your request, not a sales bot
- Clear scope, timeline and estimate within one business day
- Free 30-minute discovery call, no obligation
- NDA available on request
- Emailhello@codefreex.com
- CallUSA +1 (209) 375-3475 · India +91 790 3375 530
- Prefer to talk?Book a 30-minute call
Weakness data from the Common Weakness Enumeration (CWE®) version 5.0, Copyright © 2006–2026, The MITRE Corporation. CWE is free to use by any organization or individual for any research, development, and/or commercial purposes under the CWE Terms of Use. CWE is a registered trademark of The MITRE Corporation. The business impact, risk profile and plain-English guidance on this page are written by Codefreex and are general information, not a security assessment of your system.