Ahmad Mugheera describes a HackerOne hunt where two default IIS pages led to short-name scanning, wordlist fuzzing, and a discovered build.xml file. The writeup says that file exposed paths such as inspection.aspx, research.aspx, and test-related source entries, and that a missed group parameter later produced database errors and time-based SQL injection behavior. The strongest part is the workflow chain, though the article’s proof is still mostly the author’s account plus screenshots rather than independent validation.