| name | cache-attack |
| description | Poison CDN cache or deceive when X-Cache header is detected. |
| version | 1.1.0 |
| revision_date | "2026-07-25T00:00:00.000Z" |
| license | MIT |
| platforms | ["linux"] |
| compatibility | Requires curl |
| tags | ["recon","cache-poisoning","WCD","web-cache","CDN"] |
| category | recon |
| related_skills | ["wp-mass-recon","cors-credential-wordpress","staging-subdomain-hunt"] |
Cache Attack Skill
Web Cache Poisoning (WCP) and Web Cache Deception (WCD) methodology. WCP poisons cached pages with malicious content served to other users. WCD tricks the cache into storing sensitive pages that the attacker can then read. Both techniques exploit CDN and reverse-proxy caching behavior on CloudFront, Cloudflare, Fastly, Varnish, and Nginx.
When to Use
- Target uses a CDN (CloudFront, Cloudflare, Fastly) or reverse proxy (Varnish, Nginx cache).
- Headers show
X-Cache, Age, cf-cache-status, or X-Cache-Hits.
- After surface recon finds no direct vulnerabilities — pivot to infrastructure layer.
- Target allows file extension manipulation in URL paths (.css, .json, .js).
Prerequisites
terminal with curl.
- Cache buster parameter for safe testing (
?cb=RANDOM).
- Patience: cache poisoning requires precise timing and may need multiple attempts.
How to Run
curl --max-time 30 --connect-timeout 10 -skI "https://TARGET/" | grep -iE "age|x-cache|cf-cache-status|via|server"
curl --max-time 30 --connect-timeout 10 -skI "https://TARGET/?cb=TEST1" | grep -iE "x-cache|cf-cache-status"
curl --max-time 30 --connect-timeout 10 -skI "https://TARGET/?cb=TEST1" | grep -iE "x-cache|cf-cache-status"
curl --max-time 30 --connect-timeout 10 -skI "https://TARGET/" -H "X-Forwarded-Host: evil.com" | grep -i "location\|evil.com"
Quick Reference
Web Cache Poisoning (WCP) — attacker poisons cache for victims
| Reflection Location | Impact | Severity |
|---|
<link rel="canonical"> | SEO poisoning | Medium |
<script src="..."> |