auth-review

Audit authentication and authorization code for IDOR, token, and session vulnerabilities.

15|3|Updated Jul 9, 2026
One-click install
npx skills add https://github.com/kiurakku/cursor-kit-for-ai --skill auth-review-kiurakku
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auth-review
Source: https://github.com/kiurakku/cursor-kit-for-ai/tree/main/plugins/security/skills/auth-review
Command: npx skills add https://github.com/kiurakku/cursor-kit-for-ai --skill auth-review-kiurakku

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Authentication and authorization bugs — especially IDOR and missing ownership checks — are the most common real-world breach causes, yet they slip through generic code review. This Skill provides a structured audit playbook that separates authz from authn and demands proof-of-exploit for every finding. ## Core Features & Use Cases - Authorization-first audit: Systematically hunts IDOR by checking whether every query filters by the authenticated principal, including list endpoints, mutations, and multi-tenant scoping. - Authentication checklist coverage: Reviews password hashing, JWT signature verification, refresh token rotation, session fixation, reset flows, and OAuth state handling. - Active verification commands: Supplies curl-based tests with two accounts to prove IDOR, missing auth, and mass-assignment privilege escalation. - Use Case: Before shipping a SaaS API, run the review to confirm user A cannot read user B's orders, tokens expire correctly, and password reset tokens are single-use. ## Quick Start Ask the AI to run an auth review on your API endpoints, checking for IDOR, JWT verification, and session handling issues.

Frequently Asked Questions about auth-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check my API for IDOR vulnerabilities?▼

For every endpoint touching an owned resource, verify the database query filters by the authenticated user's ID, not just the resource ID. Test with two accounts: request user B's resource with user A's token and confirm it returns 403 or 404.

How to review JWT authentication security in code?▼

Confirm the signature is actually verified with a pinned algorithm, tokens are short-lived, refresh tokens rotate and are revocable server-side, and claims exclude PII. Also check that decode(verify=False) or alg:none acceptance does not appear anywhere.

What is the difference between authentication and authorization review?▼

Authentication verifies identity (passwords, tokens, sessions), while authorization checks what an authenticated user may do. Most real breaches come from authorization bugs like IDOR, so this review audits authorization first.

Why is localStorage risky for storing auth tokens?▼

localStorage is readable by any JavaScript on the page, so a single XSS flaw exposes tokens. httpOnly, Secure, SameSite cookies are preferred, though they then require CSRF protection.

What makes a password reset flow secure?▼

Reset tokens must be single-use, random, short-lived (under one hour), and stored hashed. All existing sessions and refresh tokens should be invalidated when the password changes, and the flow must not reveal whether an email exists.