githubEdit

Web App Enumeration Methodology

1) Check page source code for secret pages, plugin versions, interesting comments made by the developers, hidden subdomains, and interesting .js files.

Right-click on the page, then choose "View page source code"

In the page source code, press CTRL+F to use the search function and search for interesting comments.

<!--

2) If we find a WordPress installation, use wpscan

wpscan --url http://domain.local/wordpress -e ap

3) If we find an admin login portal, try default credentials like

admin:admin
admin:password
admin:password123
admin:password123456
root:root
root:toor

4) Check server version, web app technologies, and version using the Wappalyzer plugin, then search for vulnerabilities using Google or searchsploit.

For example

searchsploit search "WordPress 5.5" 

5) Directory enumeration

Wordlists

Tools:

Ffuf

Feroxbuster

Then, based on the word count, size count, etc, filter for false positives.

6) Endpoint fuzzing

Fuzz potentially vulnerable endpoints to discover vulnerabilities like LFI, SSRF, etc.

7) Parameter fuzzing

LFI

Authenticated fuzzing

WHEN IN DOUBT, OPEN UP BURPSUITE. YOU CAN ALSO BRUTE-FORCE PARAMETERS WITH INTRUDER.

8) Vulnerability Scan (if all else fails and want to look for a vulnerability like Shellshock for example)

9) After user enumeration via any means and want to brute-force, instead of using your usual wordlist, you can create custom wordlists if you find parts of the website that contain a lot of words that could be used in a wordlist

10) Vhost fuzzing

If we are working with a domain name, it coule be worth checking for other vhosts on the machine to discover an entirely new attack surface.

After discovering valid vhosts, add them to your /etc/hosts file

Last updated