Attacking Common Applications
Directory map
WordPress
Drupal
Joomla
Tomcat
Summary
Attacking common applications begins with a structured discovery phase before any exploitation is attempted. Nmap sweeps the scope list for common web ports (80, 443, 8000, 8080, 8180, 8888, 10000) using --open -oA to produce XML output that downstream tools can consume directly. A follow-up service version scan (-sV) fingerprints what is actually running — frequently revealing Splunk, PRTG, Tomcat, or other management interfaces on non-standard ports that are easily missed.
EyeWitness (eyewitness --web -x web_discovery.xml) and Aquatone (cat web_discovery.xml | ./aquatone -nmap) both accept Nmap XML and produce HTML screenshot reports, grouping targets into categories such as “High Value Targets.” These reports rapidly surface default-credential login pages (Tomcat Manager, Splunk, PRTG) and default install pages that confirm software versions without manual browsing across dozens of hosts.
When interpreting results, prioritize applications with known default credentials or recent CVEs: Tomcat Manager enables WAR-based RCE, Splunk’s search engine can execute server-side scripts, PRTG has authenticated RCE vulnerabilities in older versions, and osTicket can leak internal employee/email data useful for phishing. Findings should be tracked in a hierarchical note structure (host → application → credentials → exploitation path) throughout the engagement to support the final report.