hunt-forgot-password

Detects five authentication flaws in forgot-password and account recovery flows.

4.0k|628|Updated May 5, 2026
One-click install
npx skills add https://github.com/elementalsouls/Claude-BugHunter --skill hunt-forgot-password
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-forgot-password
Source: https://github.com/elementalsouls/Claude-BugHunter/tree/main/skills/hunt-forgot-password
Command: npx skills add https://github.com/elementalsouls/Claude-BugHunter --skill hunt-forgot-password

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Password reset and account recovery flows often contain authentication flaws like username enumeration, leaked reset tokens, and token replay that manual testers miss. This Skill provides a structured testing methodology to systematically find and prove these broken-auth primitives during authorized bug hunting engagements.

Core Features & Use Cases

  • Five Detection Patterns: Tests username enumeration via response differences, reset tokens exposed in API responses, token replay after use, missing IP/session binding, and absent rate limiting.
  • Proof Criteria: Defines measurable evidence for each finding, such as response diffs between valid and invalid emails or a second successful use of a consumed token.
  • Chain Handoff: Distinguishes recovery-flow primitives from the full account-takeover chain, handing off to related skills like hunt-ato for escalation.
  • Use Case: During an authorized web app assessment, you test the forgot-password endpoint with valid and invalid emails, compare responses to confirm enumeration, then attempt token replay to demonstrate a High-severity flaw.

Quick Start

Ask Claude to test the target's forgot-password endpoint for username enumeration, token exposure, token replay, and rate limiting using this skill.

Frequently Asked Questions about hunt-forgot-password

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

FAQPage Schema
How do I test a forgot-password endpoint for username enumeration?

Submit the reset request with a clearly invalid email, then with a known-valid email, and compare the responses. Differences in message text, HTTP status code, body length, or timing confirm username enumeration.

How to check if a password reset token can be reused?

Complete a full reset cycle, then immediately submit the same token again to the reset endpoint. If the second submission returns success, the token was not invalidated after use, which is a replay vulnerability.

What makes a password reset token predictable or weak?

Tokens derived from timestamps, usernames, or sequential IDs can be brute-forced or decoded. Short numeric codes of 4-6 digits are feasible to guess when the endpoint lacks rate limiting.

Can a reset token leak through the Referer header?

Yes. When the token rides in the reset page URL and that page loads cross-origin resources like analytics or CDN images, the full URL leaks to third parties via the Referer header, enabling token theft without inbox access.

When should I use this skill instead of an account-takeover chain test?

Use this skill to find and prove individual recovery-flow primitives like enumeration or token replay. Hand off to a full ATO chain skill when you need to assemble the primitive into a complete account-takeover exploit.