Security Test: GET based CSRF¶

Description¶

Default Severity: medium

GET based CSRF is when an external site tricks a user's browser into making a GET request to another site where the user is authenticated, leveraging the browser’s automatic inclusion of credentials like cookies. This means that if your API accepts state-changing actions via GET, an attacker can potentially make changes or reveal sensitive data on behalf of a logged-in user without their consent. Developers often fall into the trap of using GET for actions that should change state, assuming GET is harmless simply because it's meant for retrieving data. If not handled carefully, this vulnerability can lead to unauthorized transactions or data breaches, so it's important to separate safe retrieval actions (GET) from actions that modify data (which should use methods like POST with proper checks).

Reference:

• https://blog.doyensec.com/2021/05/20/graphql-csrf.html

Configuration¶

Identifier: request_forgery/csrf_get_based

Examples¶

All configuration available:

checks:
  request_forgery/csrf_get_based:
    skip: false # default

Compliance and Standards¶