What problem does it solve? Security researchers and bug bounty hunters need a systematic methodology to test Next.js applications for framework-specific vulnerabilities that generic web scanners miss, such as Server Actions authorization flaws and middleware bypasses. ## Core Features & Use Cases - Framework-Specific Attack Phases: Eight structured phases covering fingerprinting, Server Actions abuse, middleware auth bypass (including CVE-2025-29927), Image Optimization SSRF, /_next/data/ IDOR, ISR cache poisoning, debug endpoint exposure, and environment variable leakage. - False-Positive Guards: Built-in validation rules prevent misreporting, such as distinguishing the image optimizer's normal 400 allowlist rejection from a real SSRF, and requiring out-of-band callbacks for confirmation. - Use Case: During a bug bounty engagement against a Next.js 14 target, follow the phases to extract the build ID, test Server Actions without a session, probe /_next/data/ endpoints for IDOR, and confirm SSRF via a unique Collaborator callback. ## Quick Start Ask the AI to hunt for Next.js vulnerabilities on an authorized target using the hunt-nextjs methodology, starting with fingerprinting and build ID extraction.