How to fix missing permissions policy on WooCommerce

Steps for WooCommerce

1. WooCommerce runs on WordPress.org, typically on Apache or Nginx — you can set the header at the server level or via plugin.
2. Easiest plugin method: Install the free 'Headers Security Advanced & HSTS WP' plugin or 'HTTP Headers' plugin from the WordPress plugin directory (Plugins → Add New → search 'Permissions Policy headers').
3. In the chosen plugin's settings page, find the Permissions-Policy field and enter your policy value: camera=(), microphone=(), geolocation=(), payment=(), usb=(), fullscreen=(self). Save.
4. Apache server-level alternative: Add to your .htaccess file (found in the WordPress root directory via FTP/File Manager): `Header always set Permissions-Policy "camera=(), microphone=(), geolocation=()"` — requires mod_headers to be enabled.
5. Nginx server-level alternative: Add to your server {} block in your nginx.conf or site config: `add_header Permissions-Policy "camera=(), microphone=(), geolocation=()" always;` then reload Nginx.
6. Verify with Chrome DevTools → Network tab → Response Headers, or use securityheaders.com.

Permissions-Policy: camera=(), microphone=(), geolocation=(), payment=(), usb=(), fullscreen=(self)

What is missing permissions policy?

The Permissions-Policy header (formerly called Feature-Policy) is a security instruction your web server sends to every visitor's browser. It acts like a bouncer's list for powerful browser features — it tells the browser exactly which features your site is allowed to use, and blocks everything else. For example, you can declare that your store never needs access to a visitor's camera, microphone, or precise location, so even if malicious code was somehow injected into your page, the browser would refuse to grant that access. Without this header, browsers apply loose default rules, leaving those features potentially available to any script running on your pages.

Missing this header is flagged under OWASP A05:2021 (Security Misconfiguration) — one of the most common vulnerability categories found on real sites. If third-party scripts (ad networks, chat widgets, analytics) or injected malicious code try to silently access a shopper's camera, microphone, or location, nothing at the browser level stops them without this header. For an ecommerce store, that is a direct privacy and trust risk: a single reported incident of covert data capture can destroy customer confidence and trigger GDPR/CCPA regulatory scrutiny. Adding this header is a low-effort, high-signal security hardening step that security auditors and increasingly Google's ranking systems look for as a mark of a trustworthy site.

See the complete Missing permissions policy guide for every platform and the full background.