AUTH-007high SeverityBroken Authentication & Access Controls
Strict Redirect URL Allowlist on OAuth Callbacks
AI code accepts a redirect query param from the user and passes it directly to router.push() or res.redirect(), enabling open redirects.
1-Click Fix Prompt for Cursor & Claude Code
Review my codebase for "Strict Redirect URL Allowlist on OAuth Callbacks" (AUTH-007). Issue: AI code accepts a redirect query param from the user and passes it directly to router.push() or res.redirect(), enabling open redirects. Remediation required: Validate redirect URLs against an allowlist of internal relative paths starting with a single forward slash. Please: 1. Locate any occurrences of this issue across my repository. 2. Refactor the code to follow production standards without breaking existing functionality. 3. Provide a clear command or step to test and verify the fix.
Why AI Assistants Write This Bug
AI code accepts a redirect query param from the user and passes it directly to router.push() or res.redirect(), enabling open redirects.
AI code generation prioritizes immediate syntax execution over production edge cases. When an assistant hits an undefined variable or strict type error, it frequently takes the path of least resistance rather than implementing standard pre-launch security patterns.
Code Comparison
Common AI Code PatternVulnerable
// Vulnerable AI-generated pattern for: Strict Redirect URL Allowlist on OAuth Callbacks
// Insecure route handler trusting body user ID (IDOR risk)
export async function POST(req: Request) {
const { userId, newEmail } = await req.json();
// BUG: Any user can modify any other user record!
await db.user.update({ where: { id: userId }, data: { email: newEmail } });
return Response.json({ success: true });
}Launch-Ready Fix
// Production-ready fix for: Strict Redirect URL Allowlist on OAuth Callbacks
// Protected route deriving identity from verified session
export async function POST(req: Request) {
const session = await auth();
if (!session?.user?.id) {
return Response.json({ error: "Unauthorized" }, { status: 401 });
}
const { newEmail } = await req.json();
// Scoped strictly to authenticated session user ID
await db.user.update({ where: { id: session.user.id }, data: { email: newEmail } });
return Response.json({ success: true });
}Remediation & Verification Checklist
Remediation: Validate redirect URLs against an allowlist of internal relative paths starting with a single forward slash.
- Search your codebase for pattern matching "Strict Redirect URL Allowlist on OAuth Callbacks".
- Apply the recommended remediation: Validate redirect URLs against an allowlist of internal relative paths starting with a single forward slash.
- Run local build and test commands to ensure no regressions.
- Verify in your browser or with curl that the issue is resolved.
Audit All 108 Checks in One Click
Checking items one by one takes hours. Let us do it in 2 minutes.
With the Founder Pass ($15 one-time), we automatically scan your repository for this issue, plus all other 107 launch checks across secrets, Stripe webhooks, Supabase RLS, and security headers.