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/thefear078/cursor-kit-for-ai --skill auth-review-thefear078
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: auth-review
Source: https://github.com/thefear078/cursor-kit-for-ai/tree/main/plugins/security/skills/auth-review
Command: npx skills add https://github.com/thefear078/cursor-kit-for-ai --skill auth-review-thefear078

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Most real-world breaches come from boring authorization bugs like IDOR and missing permission checks rather than exotic crypto failures, and these flaws are easy to miss in code review. This Skill provides a structured audit playbook that separates authentication from authorization and actively tests both layers. ## Core Features & Use Cases - Authorization-first audit: Hunts IDOR by checking whether every query filters by the authenticated principal, including list endpoints, mutations, and multi-tenant scoping. - Authentication review: Covers password hashing, JWT signature verification, refresh token rotation, session fixation, reset flows, and OAuth account linking. - Active verification: Uses two test accounts and curl commands to prove findings with real requests rather than speculation. - Use Case: Before shipping a SaaS API, run this audit to confirm user A cannot read user B's orders, tokens expire correctly, and mass-assignment cannot promote a user to admin. ## Quick Start Review the authentication and authorization logic in this codebase and report any IDOR, token, or session vulnerabilities with proof-of-concept requests.

Frequently Asked Questions about auth-review

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

FAQPage Schema
How do I find IDOR vulnerabilities in an API?▼

Check whether every endpoint touching an owned resource filters the query by the authenticated principal, such as Order.user_id == current_user.id. Then actively test with two accounts: request user B's resource ID using user A's token and confirm it returns 403 or 404.

What should I check when reviewing JWT authentication?▼

Verify the signature is actually validated, alg: none is rejected, and the algorithm is pinned server-side. Access tokens should be short-lived, refresh tokens rotated and revocable, and claims like exp, iat, aud, and iss checked.

Should auth tokens be stored in cookies or localStorage?▼

httpOnly, Secure, SameSite cookies are preferred because localStorage is readable by XSS attacks. Once cookies carry authentication, CSRF protection becomes required, so the trade-off must be handled explicitly.

Why is account linking by email dangerous in OAuth login?▼

Linking accounts by unverified email lets an attacker merge their account into a victim's. Only link by verified email, enforce the state parameter against CSRF, and exact-match allowlist redirect URIs.

What are the limits of a manual auth code review?▼

Reading code alone misses runtime behavior, so findings require demonstrated exploit requests with test accounts. Edge-layer concerns like distributed rate limiting belong to a separate WAF review, and secrets handling needs a dedicated secrets audit.