Permissions-Policy Header Missing
No Permissions-Policy header restricts which powerful browser features, such as the camera, microphone or geolocation, the application's pages and embedded frames may use.
| Severity | Informational |
| CVSS 3.1 | 0 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:N/A:N Open in the calculator |
| CVSS 4.0 | 0 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-693: Protection Mechanism Failure |
| OWASP Top 10 | A06:2025 Insecure Design |
| Category | Security Misconfiguration |
Description
The Permissions-Policy response header lets a site declare which browser features its pages, and the frames they embed, may use: for example the camera, microphone, geolocation, payment requests, fullscreen display and USB devices. A feature disabled in the policy cannot be used by the page or its frames, whatever script runs there. The application does not send the header, so each feature falls back to the browser's default, which typically allows the page itself and same-origin frames to request it and requires a cross-origin frame to be granted it through the frame's allow attribute.
The missing header has no direct impact. If an attacker were able to run script in the application, through cross-site scripting or a compromised third-party script, or if an embedded frame were malicious, an explicit policy would stop that script requesting features the application never uses, such as the camera, microphone or location. Features that need the user's consent would still prompt the user, who would have to grant any such request, so the header is a hardening measure that limits what injected or third-party script could ask for, rather than a fix for a vulnerability. It is of most value in applications that embed third-party content.
Support varies between browsers, and the older Feature-Policy header that it replaced used a different syntax. The issue is identified by inspecting response headers; scanners report it as a missing security header.
Remediation
Send a Permissions-Policy header that disables every feature the application does not use and limits those it does use to its own origin, and grant features to embedded frames only through their allow attribute where needed.
On IIS, add the same header under customHeaders in web.config. Where a feature is needed, allow it for the application's own origin only, for example geolocation=(self). Confirm the fix by checking that the header is present on HTML responses with the intended directives.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.