webPromedium
Lab 181 — PostFlow — Stored XSS via Cache Poisoning
hackadvisor
Task: Express.js blogging platform behind nginx reverse proxy; X-Forwarded-Host header reflected unsanitized in canonical link tags, nginx caches responses with unkeyed X-Forwarded-Host, admin bot visits reported posts. Solution: poison nginx cache with XSS payload in X-Forwarded-Host header, trigger admin bot via post report, exfiltrate admin's flag cookie via same-origin comments API.
$ ls tags/ techniques/
xssstored_xssnginxexpressadmin_botcookie_exfiltrationsame_origin_exfiltrationx_forwarded_hostweb_cache_poisoningcache_key_manipulationunkeyed_headercanonical_link
honeypot_flag_identificationweb_cache_poisoning_via_unkeyed_x_forwarded_host_headerxss_attribute_breakout_in_canonical_link_tagspace_free_javascript_payload_constructionsame_origin_cookie_exfiltration_via_comments_apiadmin_bot_exploitation_via_post_reportcache_race_timing_for_poisoning
🔒
Permission denied (requires tier.pro)
Sign in to access full writeups
Sign in with GitHub to continue. No email required.
$sign in$ grep --similar
Similar writeups
- [web][Pro]Lab 183 — ArticleFlow — Stored XSS via Fat GET Cache Poisoning— hackadvisor
- [web][Pro]Lab 72 — WriteFlow — Stored XSS via WYSIWYG Editor Sanitizer Bypass— hackadvisor
- [web][Pro]Lab 163 — PostFlow — Unrestricted File Upload via Avatar Feature— hackadvisor
- [web][Pro]Lab 375 — PageFlow — Web Cache Deception via Path Normalization— hackadvisor
- [web][Pro]Lab 153 — FlowDesk — CSRF Account Takeover via Email Change— hackadvisor