Cross-Site Request Forgery (CSRF) testing, proven
Cross-Site Request Forgery (CSRF) (CSRF) — what it is, why a signature scanner misses the cases that matter, and how SuperPentest proves it with a controlled test, clean-session reproduction and hash-chained evidence mapped to A01: Broken Access Control.
CSRF is a vulnerability class scanners only partly reach — here is what it is, why that is, and how SuperPentest proves it on your app.
What CSRF is
CSRF makes a logged-in user’s browser perform an unwanted state-changing action — transferring funds, changing an email, inviting an admin — because the application trusts the session cookie without a per-request token. It turns a victim’s authenticated session into the attacker’s tool.
What it looks like
A logged-in admin visits an attacker's page that auto-submits a hidden form to POST /team/invite. With no per-request token and a session cookie the browser attaches automatically, the app invites [email protected] as an admin — the victim never clicked anything.
Why a scanner misses it
A scanner can note a missing CSRF token, but it cannot tell whether that endpoint actually performs a sensitive action, whether an alternative protection (SameSite, custom header) is enforced, or whether the token is validated server-side. Confirming exploitability needs a real cross-origin request replayed against the live flow.
How SuperPentest proves it
SuperPentest treats CSRF the way an attacker does, in four steps: it understands the business rule the feature is meant to enforce, runs a controlled test against it, then reproduces any candidate from a clean session — a fresh login with no leftover state — and finally records the impact with hash-chained request/response evidence mapped to the control it breaks. Nothing is reported as a finding until that clean-session reproduction succeeds; a candidate is not a finding.
- Understand — map the feature and the rule it should enforce.
- Controlled test — exercise the class safely, within the authorized scope.
- Clean-session reproduction — break in again from a fresh session to rule out flukes and stale state.
- Impact + evidence — hash-chained request/response, mapped to A01: Broken Access Control and your compliance controls.
Where it fits in coverage
Cross-Site Request Forgery (CSRF) is one of the 35 vulnerability classes the engine tests every run, driven through 40+ specialist tools orchestrating 13 industry-standard open-source scanners. See the full coverage map or the 35 classes explained.
Related vulnerability classes
IDOR testing · WebSocket testing · SQLi testing · XSS testing.
FAQ
Can a scanner find CSRF?
A scanner finds some cases, but misses the ones that matter — behind authentication, blind variants, or anything needing a multi-step workflow — and raises false positives on the rest. SuperPentest verifies each candidate before it counts.
How do I know a reported CSRF finding is real?
Every finding is reproduced from a clean session with hash-chained request/response evidence you can replay. If a run cannot complete the checks, it is stamped degraded coverage rather than passed as clean. See how findings are verified →
Test your app for CSRF. Book a demo or request an evaluation account. See the sample report.