Skip to main content
MediumHeadersOWASP A05:2021CWE-1021

How to fix: Invalid X-Frame-Options Value

X-Frame-Options has invalid value.

Why it matters

Clickjacking protection may not work.

Only DENY, SAMEORIGIN, ALLOW-FROM are valid.

How to fix it

  1. 1Use DENY or SAMEORIGIN for X-Frame-Options.

Code examples

Set X-Frame-Options to a valid value

JavaScript
// Valid values: DENY, SAMEORIGIN
// X-Frame-Options: ALLOW-FROM is deprecated, use CSP frame-ancestors instead
// next.config.mjs
export default {
  async headers() {
    return [{ source: "/(.*)", headers: [{ key: "X-Frame-Options", value: "DENY" }] }];
  },
};
// Or with CSP (preferred):
// Content-Security-Policy: frame-ancestors 'none'

References

Detected automatically by VulnRadar. The check id is x-frame-options-invalid, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is Invalid X-Frame-Options Value?
VulnRadar rates this medium severity in the headers category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id x-frame-options-invalid, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Invalid X-Frame-Options Value map to?
It maps to CWE-1021. In the OWASP Top 10 it falls under A05:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for invalid x-frame-options value

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: Invalid X-Frame-Options Value | VulnRadar