Clickjacking
Also called UI Redressing.
Tricking users into clicking hidden elements via overlaid framing.
What it is
An attack that loads a target site in a transparent or disguised frame over decoy content, so the victim's clicks are silently delivered to the hidden interface, performing actions they did not intend.
Why it matters
It can trigger sensitive operations using the victim's authenticated session, and the standard defenses (frame-busting headers and a strong CSP frame-ancestors policy) are common things to check for during a review.
In practice
A fake 'play' button overlaying an invisible 'confirm' control on a banking page beneath it.
What to look for
- Pages that load inside a frame on another site.
- Missing frame-ancestors or X-Frame-Options headers.
- Sensitive buttons that can be framed.
Common mistake
Using JavaScript frame busting. Use the frame-ancestors header instead.
Practice it nearby
CyberKit has no tool for this term itself. These are the closest places to practice it.
- Email Header Analyzer
Walk the Received chain, and read the SPF, DKIM and DMARC verdicts.
- Phishing Case
A reported invoice email: pull the deciding values out of its raw headers, and say what they establish.
In the field
Well-known tools where this shows up on the job. They are listed to show the landscape, not as a recommendation.
-
Burp Suite Commercial
An intercepting proxy for testing web apps by hand and with its scanner.
-
ZAP Open source
An open source web app scanner and proxy, often run in CI pipelines.
-
Cloudflare WAF Commercial
Blocks common web attacks at the edge while the code gets fixed.
Read next
- Security Headers: HTTP response headers that harden the browser's handling of a site.
- Content Security Policy: A header that restricts which sources a page may load and run.
- Cross-Site Request Forgery: Tricking a logged-in user's browser into making an unwanted request.