Legal Disclaimer:

This platform is for authorized security research and educational purposes ONLY. Scanning assets without explicit permission is illegal.

Vulnerability Intelligence

Fixing Cross-Site Request Forgery (CSRF)

Vulnerability assessment details, CWE reference metrics, and complete code-level patches.

Threat Profile

CWE ID
CWE-352
Severity
High
Methodology
Passive Audit
Audit your Website for Cross-Site Request Forgery (CSRF)

Vulnerability Analysis

CSRF occurs when a malicious website causes a victim's web browser to perform an unwanted action on a trusted site where the victim is currently authenticated. Browsers automatically attach authentication cookies to requests, validating unauthorized actions.

How it is Detected

Identified by auditing state-changing requests (POST, PUT, DELETE) to check if they lack unique, validated CSRF tokens or SameSite cookie parameters.

Remediation Guidelines

Implement unique anti-CSRF tokens for every state-changing session request. Configure session cookies with the SameSite=Strict or SameSite=Lax attributes.

Remediation Script (Cookie configuration)

// SECURE REMEDIATION: Restricting cookie visibility
Set-Cookie: session_id=xyz123; Secure; HttpOnly; SameSite=Lax

Frequently Asked Questions

How does SameSite mitigate CSRF?

SameSite tells the browser not to send cookies along with cross-site requests, blocking attackers from abusing the active session.

Are GET requests vulnerable to CSRF?

Yes. All state-changing requests must be protected, and GET requests must never alter application state.

What is an anti-CSRF token?

A unique, cryptographically secure value associated with the session that must be submitted inside request forms to verify user intent.