Loophole

When a viewer will load any file you name, do not stop at system files like the user list. Aim it at the application's own code and configuration. A developer in a hurry often leaves database and service passwords hard coded there, and a scripting file that would normally run can be coaxed into handing you its raw text instead of executing.

We can't always easily access the "juicy stuff" when exploring File Inclusion vulnerabilities. That’s when we learn to appreciate well-executed fuzzing.