> For the complete documentation index, see [llms.txt](https://ed4m4s.blog/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ed4m4s.blog/master-1/http-enum/checklist.md). # CheckList ### CheckList *Lots of strategies:* * Check server name for vulnerability, usually a software will be running with a vulnerability, lots of googling required * Try to read the exploit code, most of the time it will give a hint whether you’re in the right spot or not * Run dirbuster, nikto, dirsearch, ffuf etc * Check the response size and manually check for the webpage in the dirbuster output i.e. don’t assume stuff, nikto is prone to false positives as well keep in mind, but nikto can spot the put functionality enabled so as soon as you see a file server type layout webserver , run nikto * Enumerate for shell shock vulnerabilities. * Login page found?, google for default creds ,try logically finding the username password using cewl * Check for sql injection * Check the URL for LFI,RFI * Once logged in, try searching for the file manager to upload shell. Sometimes you wouldn’t need to login for an exploit to work i.e. it can be a rabbit hole if you are able to login easily so read the exploit code properly. * Wordpress use wpscan, Joomla use joomscan, Drupal use droopscan . * The answer is simpler than you think!!!!!!!!!!!! --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ed4m4s.blog/master-1/http-enum/checklist.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.