CWE-352: Cross-Site Request Forgery (Cross Site Reference Forgery), page 199
Filter
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
What the weakness is: CWE-352 at MITRE. OWASP Top 10: A01:2025 Broken Access Control
Related attack patterns (CAPEC): 4
- CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
- CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
- CAPEC-462 Cross-Domain Search Timing Severity: Medium
- CAPEC-467 Cross Site Identification Severity: Low
The attack patterns MITRE's CAPEC relates to CWE-352, as MITRE names them. Credits.
Ask an AI about CWE-352
Show the prompt
Explain CWE-352: Cross-Site Request Forgery and how to prevent and detect it in code. Use https://cwe.mitre.org/data/definitions/352.html and https://cve.bz/cve/cwe/352?via=ask-ai-copy for recent CVEs with this weakness. Cite the sources.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this weakness's id and public links.
- –CVE-2002-2426EPSS 0.7%
Cross-site request forgery (CSRF) vulnerability in Citrix Presentation Server 4.0 and 4.5, MetaFrame Presentation Server 3.0, and Access Essentials 1.0 through 2.0 allows remote attackers to execute arbitrary published applications, and po…