Skip to main content
LowHeadersOWASP A05:2021CWE-693

How to fix: Missing Permissions-Policy Header

The Permissions-Policy (formerly Feature-Policy) header is not set.

Why it matters

Third-party scripts or iframes could access powerful browser APIs like camera, microphone, or geolocation.

Permissions-Policy allows you to selectively enable or disable browser features for your page and any embedded iframes.

How to fix it

  1. 1Add a Permissions-Policy header that disables features you don't use.
  2. 2Common features to restrict: camera, microphone, geolocation, payment, usb.
  3. 3Set features to () (empty) to disable, or self to allow only same-origin.

Code examples

Next.js

JavaScript
const nextConfig = {
  async headers() {
    return [{
      source: '/(.*)',
      headers: [{ key: 'Permissions-Policy', value: 'camera=(), microphone=(), geolocation=(), payment=()' }],
    }];
  },
};

Nginx

nginx
add_header Permissions-Policy "camera=(), microphone=(), geolocation=(), payment=()" always;

Apache

APACHE
Header always set Permissions-Policy "camera=(), microphone=(), geolocation=(), payment=()"

Caddy

PLAINTEXT
header Permissions-Policy "camera=(), microphone=(), geolocation=(), payment=()"

Express (Node.js)

JavaScript
app.use((req, res, next) => {
  res.setHeader('Permissions-Policy', 'camera=(), microphone=(), geolocation=(), payment=()');
  next();
});

Deno (Hono)

TypeScript
app.use('*', async (c, next) => {
  await next();
  c.header('Permissions-Policy', 'camera=(), microphone=(), geolocation=(), payment=()');
});

Bun (Elysia)

TypeScript
app.onAfterHandle(({ set }) => {
  set.headers['Permissions-Policy'] = 'camera=(), microphone=(), geolocation=(), payment=()';
});

References

Detected automatically by VulnRadar. The check id is permissions-policy-missing, stable across every scan so you can filter or diff on it.

See every headers check

Questions

How severe is Missing Permissions-Policy Header?
VulnRadar rates this low 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-missing, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Missing Permissions-Policy Header 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.

Propose a checkHow a check is built

Scan your own site for missing permissions-policy header

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: Missing Permissions-Policy Header | VulnRadar