• Authentication
CSRF (Cross-Site Request Forgery)
CSRF forces a victim’s browser to send an authenticated request to your site without their intent — changing email, transferring funds, or altering settings while they are logged in.
How attackers abuse it
If state-changing endpoints trust session cookies alone and lack anti-CSRF tokens or equivalent, an attacker’s page can trigger POST/PUT/DELETE via forms or simple requests.
Login CSRF and “change email” CSRF are common high-impact variants. SameSite cookie attributes reduce some cases but are not a complete substitute for explicit request authentication on sensitive actions.
APIs that accept cookie auth from browsers inherit classic CSRF risks unless they require custom headers or tokens attackers cannot read cross-origin.
What proof looks like
Proof is a cross-origin (or attacker-controlled page) request that successfully changes state using the victim’s session in a test account — demonstrating missing CSRF defenses on that endpoint.
In PandaONE, this class maps to the Authentication finding category. Alerts ship only with evidence — never as unverified scanner noise.
How to prevent it
- Use synchronized anti-CSRF tokens or double-submit cookies on state-changing routes.
- Prefer Authorization headers / bearer tokens for SPA APIs instead of cookie-only auth where practical.
- Set SameSite=Lax or Strict on session cookies; still protect critical POSTs explicitly.
- Require re-authentication for high-risk account changes.
- Reject unexpected Content-Types and enforce CORS tightly for credentialed APIs.
• Related tools
• Glossary
• Related pages
Hunt this class with proof
Or scan your domain.