ffuf & web content fuzzing
When it applies
You have an in-scope web target (tradecraft-scope-roe) and need what the site map doesn't show:
hidden directories and files, undocumented GET/POST parameters, or name-based virtual hosts. This is
the active half of recon-content-discovery — wordlist-driven, noisy, and governed by roe.md rate
limits.
Why it works
ffuf replaces the FUZZ keyword anywhere in a request — path, query, body, header — with each
wordlist entry, then classifies responses by status/size/word-count. Discovery is a filtering
problem: a wildcard or SPA route answers 200 to everything, so the skill is teaching ffuf what
"nothing found" looks like, then listing only the deviations.
Method
- Directory/file brute force with an extension set matched to the stack:
ffuf -u http://target.com/FUZZ -w /usr/share/seclists/Discovery/Web-Content/raft-medium-directories.txt
ffuf -u http://target.com/FUZZ -w wordlist.txt -e .php,.html,.txt
ffuf -u http://target.com/FUZZ -w wordlist.txt -recursion -recursion-depth 2
- Calibrate the noise floor — run once, note the junk response's status/size/words, then filter:
-mc 200,301,302 (match codes), -fs 1234 (hide size), -fc 403, or just -ac to auto-calibrate
against random canary words. Without this step every wildcarded app "finds" thousands of pages.
- Parameter discovery:
ffuf -u "http://target.com/api?FUZZ=test" -w /usr/share/seclists/Discovery/Web-Content/burp-parameter-names.txt -fs 0
ffuf -u http://target.com -X POST -d "user=FUZZ&pass=test" -w wordlist.txt
- Virtual hosts — whole apps hide behind one IP, answering only to the right
Host: name:ffuf -u http://target.com -H "Host: FUZZ.target.com" -w subdomains.txt -fs 0
The default vhost answers everything with the same 200 — filter by the different size/words.
- Carry auth when testing behind login — replicate the session:
-H "Cookie: session=abc" / -H "Authorization: Bearer token".
- Switch tools when the fit is better:
feroxbuster -u https://target.com -w raft-medium-directories.txt -d 3 -C 403,404 -x php,asp,html --rate-limit 50
feroxbuster -u https://target.com --auto-tune --smart # self-tuning filters/rate
gobuster dir -u http://target.com -w common.txt -x php,txt -b 404,403
gobuster dns -d target.com -w subdomains.txt # DNS-mode subdomain brute
dirsearch -u https://target.com -e php,asp,aspx,jsp -r -R 3 --exclude-status=403,404
wfuzz -c -z file,big.txt --hc 404 https://target.com/FUZZ # FUZZ/FUZ2Z multi-payload
feroxbuster = recursion by default; gobuster = simple and steady (+ DNS mode); dirsearch = sane
defaults; wfuzz = multi-wordlist combos (-z file,a -z file,b).
- Feed results back — discovered paths go to the Burp/
web-* testing loop; discovered params
go to arjun for confirmation and then to the relevant injection skills.
Gotchas
- Unfiltered output is fiction — a "1000 hits" run against a wildcard app is 1000 copies of the
same 200. Calibrate first (
-ac or manual -fs/-fc/-fw), then trust the short list.
- SPA catch-alls — any-path-200 with identical body size means a frontend router, not real
endpoints; filter by size and move on.
- Rate limits and WAFs — default ffuf speed trips Cloudflare/ModSecurity and breaches many
bug-bounty RoEs; use
-rate/-p (delay) and check roe.md before launching.
- Recursion explodes — depth 3 on a big wordlist × every found dir can run for hours; cap with
-recursion-depth and scope recursion to interesting dirs.
- Windows/curl quirk — when verifying hits with curl,
[] in URLs (e.g. __proto__[test])
needs --globoff or curl misparses them as ranges.
- Match the wordlist to the stack — raft/directory-list for general, CMS-specific lists after
fingerprinting (
recon-techstack-fingerprinting), burp-parameter-names for params,
subdomains-top1million-5000 for vhosts.
Verify success
Every reported path/param/vhost is manually re-requested (curl/Burp) and returns content that
differs from the calibrated baseline — a page of unverified scanner hits is a lead list, not a
result.
References
ffuf GitHub; SecLists wordlists; feroxbuster/gobuster/dirsearch/wfuzz docs. Discovery methodology:
recon-content-discovery; full web toolbelt: web-arsenal; pipeline: automation-recon-pipeline.
Portions adapted from reverse-skill by zhaoxuya520, MIT License.
1---2name: tools-ffuf3description: >4 Fuzz web targets with ffuf for content, parameter, and vhost discovery — FUZZ keyword placement in5 paths, query strings, POST bodies and Host headers, matcher/filter calibration (-mc/-fs/-ac),6 recursion, and when to switch to feroxbuster/gobuster/dirsearch. Load when a web target needs hidden7 paths, files, parameters, or virtual hosts enumerated. Signals: ffuf -w FUZZ, directory brute force,8 gobuster dir, feroxbuster, dirsearch, raft-medium-directories, burp-parameter-names, 404 filtering.9domain: tools10type: technique11stability: learning12modes: [pentest, bugbounty]13severity: info14mitre: [T1595.003]15tools: [ffuf, gobuster, feroxbuster, dirsearch, wfuzz]16schema_version: 117metadata:18 source: https://skillmd.com/skills/noorqureshi/tools-ffuf19---2021# ffuf & web content fuzzing2223## When it applies24You have an in-scope web target (`tradecraft-scope-roe`) and need what the site map doesn't show:25hidden directories and files, undocumented GET/POST parameters, or name-based virtual hosts. This is26the active half of `recon-content-discovery` — wordlist-driven, noisy, and governed by `roe.md` rate27limits.2829## Why it works30ffuf replaces the `FUZZ` keyword anywhere in a request — path, query, body, header — with each31wordlist entry, then classifies responses by status/size/word-count. Discovery is a filtering32problem: a wildcard or SPA route answers 200 to *everything*, so the skill is teaching ffuf what33"nothing found" looks like, then listing only the deviations.3435## Method361. **Directory/file brute force** with an extension set matched to the stack:37 ```bash38 ffuf -u http://target.com/FUZZ -w /usr/share/seclists/Discovery/Web-Content/raft-medium-directories.txt39 ffuf -u http://target.com/FUZZ -w wordlist.txt -e .php,.html,.txt40 ffuf -u http://target.com/FUZZ -w wordlist.txt -recursion -recursion-depth 241 ```422. **Calibrate the noise floor** — run once, note the junk response's status/size/words, then filter:43 `-mc 200,301,302` (match codes), `-fs 1234` (hide size), `-fc 403`, or just `-ac` to auto-calibrate44 against random canary words. Without this step every wildcarded app "finds" thousands of pages.453. **Parameter discovery:**46 ```bash47 ffuf -u "http://target.com/api?FUZZ=test" -w /usr/share/seclists/Discovery/Web-Content/burp-parameter-names.txt -fs 048 ffuf -u http://target.com -X POST -d "user=FUZZ&pass=test" -w wordlist.txt49 ```504. **Virtual hosts** — whole apps hide behind one IP, answering only to the right `Host:` name:51 ```bash52 ffuf -u http://target.com -H "Host: FUZZ.target.com" -w subdomains.txt -fs 053 ```54 The default vhost answers everything with the same 200 — filter by the *different* size/words.555. **Carry auth when testing behind login** — replicate the session:56 `-H "Cookie: session=abc"` / `-H "Authorization: Bearer token"`.576. **Switch tools when the fit is better:**58 ```bash59 feroxbuster -u https://target.com -w raft-medium-directories.txt -d 3 -C 403,404 -x php,asp,html --rate-limit 5060 feroxbuster -u https://target.com --auto-tune --smart # self-tuning filters/rate61 gobuster dir -u http://target.com -w common.txt -x php,txt -b 404,40362 gobuster dns -d target.com -w subdomains.txt # DNS-mode subdomain brute63 dirsearch -u https://target.com -e php,asp,aspx,jsp -r -R 3 --exclude-status=403,40464 wfuzz -c -z file,big.txt --hc 404 https://target.com/FUZZ # FUZZ/FUZ2Z multi-payload65 ```66 feroxbuster = recursion by default; gobuster = simple and steady (+ DNS mode); dirsearch = sane67 defaults; wfuzz = multi-wordlist combos (`-z file,a -z file,b`).687. **Feed results back** — discovered paths go to the Burp/`web-*` testing loop; discovered params69 go to arjun for confirmation and then to the relevant injection skills.7071## Gotchas72- **Unfiltered output is fiction** — a "1000 hits" run against a wildcard app is 1000 copies of the73 same 200. Calibrate first (`-ac` or manual `-fs/-fc/-fw`), then trust the short list.74- **SPA catch-alls** — any-path-200 with identical body size means a frontend router, not real75 endpoints; filter by size and move on.76- **Rate limits and WAFs** — default ffuf speed trips Cloudflare/ModSecurity and breaches many77 bug-bounty RoEs; use `-rate`/`-p` (delay) and check `roe.md` before launching.78- **Recursion explodes** — depth 3 on a big wordlist × every found dir can run for hours; cap with79 `-recursion-depth` and scope recursion to interesting dirs.80- **Windows/curl quirk** — when verifying hits with curl, `[]` in URLs (e.g. `__proto__[test]`)81 needs `--globoff` or curl misparses them as ranges.82- **Match the wordlist to the stack** — raft/directory-list for general, CMS-specific lists after83 fingerprinting (`recon-techstack-fingerprinting`), `burp-parameter-names` for params,84 `subdomains-top1million-5000` for vhosts.8586## Verify success87Every reported path/param/vhost is manually re-requested (curl/Burp) and returns content that88differs from the calibrated baseline — a page of unverified scanner hits is a lead list, not a89result.9091## References92ffuf GitHub; SecLists wordlists; feroxbuster/gobuster/dirsearch/wfuzz docs. Discovery methodology:93`recon-content-discovery`; full web toolbelt: `web-arsenal`; pipeline: `automation-recon-pipeline`.9495---96_Portions adapted from [reverse-skill](https://github.com/zhaoxuya520/reverse-skill) by zhaoxuya520, MIT License._