Skip to content
StrikeOps

Clickjacking (Missing Frame Protection)

LowTypical severity Web applications and APIsCWE-1021

01Description

The application can be embedded in a frame on a third-party site, as neither the X-Frame-Options header nor the Content-Security-Policy frame-ancestors directive restricts framing.

02Impact

An attacker can load the application in a hidden frame on a malicious page and trick a logged-in user into clicking buttons or links within it, performing actions they did not intend.

03Severity

Typically

Low

Typically Low. Low for most pages. Medium where a framed page has sensitive one-click actions, such as changing account settings or approving transactions.

04How to verify

  1. 1Inspect responses for X-Frame-Options and CSP frame-ancestors.
  2. 2Create a simple proof-of-concept page that frames a sensitive page of the application.
  3. 3Identify which framed actions would be meaningful to an attacker.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Set Content-Security-Policy: frame-ancestors 'self' (or 'none' where framing is never needed).
  2. 2Also set X-Frame-Options: DENY or SAMEORIGIN for older browsers.
  3. 3Require confirmation for sensitive actions.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo