How to fix: Permissions-Policy grants fullscreen to every origin
The policy grants fullscreen to every origin (fullscreen=*), which includes any third party the page embeds in an iframe. A site using fullscreen itself is not reported.
Why it matters
Set Permissions-Policy: fullscreen=(self) to scope fullscreen requests to your origin
fullscreen=* lets any embedded third-party frame take over the screen, which is the ingredient a clickjacking or spoofed-UI overlay needs. fullscreen=(self) keeps the capability with the page itself. A legacy Feature-Policy header is read with its own syntax (fullscreen 'self'), which is restrictive and is not reported.
How to fix it
- 1Set Permissions-Policy: fullscreen=(self) to scope fullscreen requests to your origin
Code examples
Restrict fullscreen API in Permissions-Policy
// next.config.mjs
export default {
async headers() {
return [{ source: "/(.*)", headers: [{ key: "Permissions-Policy", value: "fullscreen=('self')" }] }];
},
};
// Only your own origin and explicitly allowed iframes can go fullscreenReferences
Detected automatically by VulnRadar. The check id is permissions-policy-fullscreen-blocked, stable across every scan so you can filter or diff on it.
More headers checks
Questions
- How severe is Permissions-Policy grants fullscreen to every origin?
- VulnRadar rates this info 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 permissions-policy-fullscreen-blocked, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does Permissions-Policy grants fullscreen to every origin map to?
- It maps to CWE-693. 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.