01Description
State-changing requests were accepted without a CSRF token or equivalent protection, and session cookies were sent with cross-site requests.
02Impact
A malicious page visited by a logged-in user can cause the user's browser to submit requests to the application, performing actions such as changing the account email or settings without the user's knowledge.
03Severity
Typically
Medium
Typically Medium. Medium where state-changing actions such as profile or email changes are affected. High where CSRF allows password changes, payments or administrative actions.
04How to verify
- 1Identify state-changing requests and check for anti-CSRF tokens and SameSite cookie attributes.
- 2Build a benign proof-of-concept page that submits the request cross-site using a test account.
- 3Confirm the action completes without user interaction beyond visiting the page.
Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.
05Remediation
- 1Use the framework's anti-CSRF token protection on all state-changing requests.
- 2Set SameSite=Lax or Strict on session cookies.
- 3Require re-authentication for sensitive actions such as password and email changes.
Draft findings like this from your own evidence
Book a demo