Every scanner flags it: "Missing X-Frame-Options header." Many programs close it as informative, and they're often right. Bugcrowd's Vulnerability Rating Taxonomy splits clickjacking into a "non-sensitive action" entry and a "sensitive click-based action" entry, and only the second one is rated above the bottom tier.
So the header on its own isn't the bug. The bug is a page that another site can frame, that arrives logged in, and that holds an action one click can complete. This post walks through how to check those three things, how to prove the result on your own test account, and how to fix it so it stays fixed.
Only test applications you own or are explicitly authorized to test. Every host below is a stand-in.
What clickjacking actually is
Clickjacking (CWE-1021, "Improper Restriction of Rendered UI Layers or Frames") loads the target page in an invisible iframe on top of a decoy page. The user thinks they're clicking "Claim prize".β¦