hunt-clickjacking

Detect and prove clickjacking vulnerabilities from missing X-Frame-Options and CSP frame-ancestors headers.

Updated Sep 6, 2026
One-click install
npx skills add https://github.com/inventashif/helpful-code-sidekick --skill hunt-clickjacking-inventashif
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-clickjacking
Source: https://github.com/inventashif/helpful-code-sidekick/tree/main/scripts/hackerai/skills/bughunter/hunt-clickjacking
Command: npx skills add https://github.com/inventashif/helpful-code-sidekick --skill hunt-clickjacking-inventashif

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Web pages that lack framing protections can be embedded in invisible iframes, letting attackers trick victims into clicking hidden buttons on sensitive pages. This Skill guides security testers through screening for missing headers and, critically, proving real exploitability in a browser rather than reporting header absence alone. ## Core Features & Use Cases - Header Screening: Fetch target pages and check for X-Frame-Options and CSP frame-ancestors to identify frameable candidates. - Browser-Based Proof of Concept: Build a minimal HTML iframe PoC and confirm the page renders framed, the victim's authenticated session survives the cross-site context, and a state-changing action is reachable. - False Positive Filtering: Distinguish real findings from non-issues caused by SameSite cookies, framebusting JavaScript, or read-only pages. - Use Case: During a bug bounty engagement, test a target's money transfer page by checking its response headers, then loading it in a hidden iframe PoC to demonstrate that an authenticated victim could be tricked into confirming a transfer. ## Quick Start Test https://target.example/account/transfer for clickjacking by checking its framing headers and proving exploitability with a browser-based iframe PoC.

Frequently Asked Questions about hunt-clickjacking

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test a website for clickjacking vulnerabilities?

Fetch the page and check response headers for X-Frame-Options or CSP frame-ancestors. If both are absent, build an HTML iframe PoC and load it in a real browser to confirm the page renders framed and a sensitive action still works.

Is a missing X-Frame-Options header enough to report clickjacking?

No, header absence alone is not a valid finding. SameSite cookies, framebusting JavaScript, or the lack of any sensitive framed action can fully defeat the attack, so a working browser-based iframe PoC is required.

Which pages are the best clickjacking targets?

The highest-value targets are state-changing pages: login flows, money transfers, checkout confirmations, account settings like email or password changes, 2FA disable actions, OAuth authorize dialogs, and admin actions.

Why does my clickjacking PoC fail even without protection headers?

The most common cause is SameSite=Lax or SameSite=Strict session cookies, which are not sent on cross-site framed requests, so the victim is unauthenticated in the iframe. Framebusting JavaScript that detects top!==self can also break the frame.

What headers prevent clickjacking attacks?

X-Frame-Options set to DENY or SAMEORIGIN blocks framing, and Content-Security-Policy frame-ancestors 'none' or 'self' provides the modern equivalent. Either mechanism, when restrictive, fully protects the page.