CyberKit

Cross-Site Request Forgery

Also called CSRF, XSRF.

Tricking a logged-in user's browser into making an unwanted request.

What it is

An attack that abuses a victim's existing authenticated session by causing their browser to send a forged state-changing request to a site they trust, without their intent. The server cannot distinguish it from a genuine action.

Why it matters

CSRF can move money, change settings, or alter accounts using the victim's own session, which is why anti-CSRF tokens and SameSite cookies matter and why their absence is a notable finding.

In practice

A hidden form on a malicious page that submits a funds-transfer request to a bank where the victim is logged in.

What to look for

  • State changing requests without a token.
  • Cookies missing SameSite settings.
  • Actions that work through GET requests.

Common mistake

Trusting the cookie alone. Use tokens or SameSite so another site cannot ride the session.

Practice it nearby

CyberKit has no tool for this term itself. These are the closest places to practice it.

In the field

Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.

  • Burp Suite Commercial

    An intercepting proxy for testing web apps by hand and with its scanner.

  • ZAP Open source

    An open source web app scanner and proxy, often run in CI pipelines.

  • Cloudflare WAF Commercial

    Blocks common web attacks at the edge while the code gets fixed.

Read next

  • Cookie Security: Cookie flags that limit theft, leakage, and cross-site sending.
  • API Security: Protecting application programming interfaces from abuse and data exposure.
  • Cross-Site Scripting: Injecting attacker script that runs in other users' browsers.

Sources