| name | cms-detection |
| description | Identify CMS, frameworks, and server technology stacks on live hosts. |
| version | 1.1.0 |
| revision_date | "2026-07-25T00:00:00.000Z" |
| license | MIT |
| platforms | ["linux"] |
| compatibility | Requires curl, httpx, nuclei |
| tags | ["recon","CMS","fingerprinting","technology","WordPress","Drupal","Joomla","Magento"] |
| category | recon |
| related_skills | ["web-enumeration","wordpress-plugin-hunt","visual-recon","wp-mass-recon"] |
CMS Detection
Identify the content management system, web framework, server software, and technology stack of every live host. Know which stack you're attacking before you attack it — a WordPress site needs different tests than a Laravel API or a Spring Boot microservice. Multi-CMS detection covers WordPress, Drupal, Joomla, Magento, Shopify, Wix, Squarespace, Laravel, Django, Express, Spring Boot, and more.
When to Use
- You have a list of alive hosts and need to categorize them by technology.
- WordPress-specific tests produced false positives (the site uses Drupal).
- Need to identify which CMS version is running to match against known CVEs.
- A host returns generic 200 on all paths — technology detection tells you what it actually runs.
- Want to find sites running outdated versions of popular CMS platforms.
Prerequisites
terminal with httpx, whatweb, wappalyzer, and curl.
- A list of alive subdomains from
skill_view(name='visual-recon') or skill_view(name='subdomain-enumeration').
Quick Detection
cat alive_subs.txt | httpx -silent -tech-detect -o tech_detect.txt
whatweb -i alive_subs.txt -a 3 -t 50 --log-brief=cms_results.txt
Procedure
Phase 1 — Bulk Technology Fingerprinting
cat alive_subs.txt | httpx -silent -tech-detect -o tech_httpx.txt
cat tech_httpx.txt | awk -F' [' '{print $2}' | tr -d ']' | tr ',' '\n' \
| sed 's/^ *//' | sort | uniq -c | sort -rn > tech_summary.txt
whatweb -i alive_subs.txt -a 3 -t 50 \
--log-brief=cms_results.txt \
--log-json=cms_results.json
cms_results.json | jq -r \
| -u > versioned_cms.txt