What problem does it solve? Security testers assessing Next.js/React SSR applications often produce false positives from framework banners or stale version hints, or accidentally cross authorization boundaries. This Skill provides an evidence-gated workflow that confirms the build, routes, data requests, caching, and version before validating public data exposure, server actions, and known advisories. ## Core Features & Use Cases - Framework Fingerprinting: Confirms Next.js build and version signals from real pages and network traffic, recording SSR/ISR/cache behavior, route handlers, server actions, middleware, and identity state. - Evidence-Gated Validation: Enforces a baseline → single-variable probe → post-baseline → oracle → evidence loop, treating WAF blocks, captchas, and scanner hits as INCONCLUSIVE rather than findings. - Safe CVE Checking: Performs version and exposure applicability checks only, explicitly prohibiting cache poisoning, server action exploitation, and RCE payloads. - Use Case: During an authorized bug bounty engagement against a Next.js application, use this Skill to verify whether a suspected server action or cache misconfiguration is a real, reproducible boundary violation before reporting it. ## Quick Start Use the hunt-nextjs skill to plan an evidence-gated, authorized validation of the Next.js target within my declared scope.
