Hi everyone,
I recently came across an interesting logic flaw while hunting on a target, and I wanted to get some advice from experienced bug hunters on whether this is considered a valid finding and how best to report it.
Here is the scenario I observed:
Account Pre-creation / Unverified Signup: The target platform allows users to sign up with any email address (e.g., [victim@example.com](mailto:victim@example.com)) without requiring immediate email verification.
Persistent Attacker Session: An attacker pre-registers an account using the victim's email and remains logged into this session.
Victim Recovery: When the actual victim tries to sign up later, they get a "user already exists" error, uses the "Forgot Password" feature, resets the password, and logs in.
The Flaw: Even after the victim resets the password and logs in, the attacker's pre-existing session remains fully active and valid (unless the victim manually triggers a profile update like changing their name). Furthermore, there is no "Active Sessions" or "Log out from all devices" dashboard for the user.
My questions for the community:
Is this specific chain generally accepted as a valid Account Takeover (ATO) or medium/high severity bug by most programs, or is pre-registration considered out-of-scope / self-mitigating?
If it is valid, what is the best way to articulate the impact and structure the Steps to Reproduce (PoC) to avoid getting closed as "Informational" or "Not Applicable"?
Any insights, tips, or past experiences with similar bugs would be greatly appreciated! Thanks in advance.