vetkit.js.csrf.protection-disabled
The framework's built-in CSRF / origin check is explicitly disabled or opened to every origin. Other sites can then submit state-changing requests on behalf of logged-in users.
Last updated:
Suite: Security
javascript, typescript
The framework's built-in CSRF / origin check is explicitly disabled or opened to every origin. Other sites can then submit state-changing requests on behalf of logged-in users.
Category: SECURITY · Engine rule severity: WARNING
How to fix it
Keep the origin check enabled and list the specific trusted origins (SvelteKit csrf.trustedOrigins, Next.js serverActions.allowedOrigins) instead of disabling it.
References
Source: packages/engine/rules/sast/javascript.yml.
Generated from shipped rule definitions at build time. Matching is a review signal, not proof of exploitability. “generic” denotes text matching, not complete language or framework coverage. Runtime configuration and available tools affect whether a rule runs.