Enforce the report-only Content-Security-Policy on WordPress

Why it matters

A report-only policy reports violations but blocks nothing, so it gives no protection yet. Once its reports are clean, send the same policy as Content-Security-Policy.

Staged change. Do this in stages and check each one before the next, so a mistake does not break your site or your mail.

The fix

1. Stage 1: check the reports or the developer console on the front end until nothing legitimate is reported.
2. Stage 2: switch the security-headers plugin from report-only to enforce, or rename the header where it is set (the server, CDN or your must-use plugin), then clear page caches.

Read the documentation ↗(opens in a new tab)

Related

• Reported by the Content-Security-Policy check
• Add a Content-Security-Policy
• Send the Content-Security-Policy as an HTTP header
• Restrict where scripts can load from
• Replace 'unsafe-inline' scripts with nonces or hashes
• Remove 'unsafe-eval' from script-src
• Remove wildcard sources from script-src
• Set object-src to 'none'
• Add base-uri to the Content-Security-Policy
• Reduce reliance on inline styles
• Fix the Content-Security-Policy syntax