WP.com - Wordpress Hosting

CSP for WP.com - Wordpress Hosting

utilities

Using WP.com - Wordpress Hosting with Content Security Policy

Directives needed for a CSP for sites hosting on WP.com . Note that you may also need to allow javascript 'eval' in the RapidSec Security Manager - based on your CSP logs.

Allow these directives in your CSP, to support WP.com - Wordpress Hosting in your Content Security Policy:

script-src
  https://*.wp.com;
style-src
  'unsafe-inline'
  *.wp.com;
frame-src
  widgets.wp.com;
img-src
  data:
  *.wp.com;
font-src
  data:
  *.wp.com;
connect-src
  *.wp.com;

The main domains used by WP.com - Wordpress Hosting are:

wp.com

Sources:

RapidSec CSP Generator(RapidSec Data Network)

Example Content-Security-Policy violations / reports:

Using the above CSP package, will fix these errors that you may be seeing in your console logs:

script-src/script-src-elem/script-src-attrviolations

Refused to load the script 'https://*.wp.com/c/*/wp-includes/js/jquery/jquery.min.js' because it violates the following Content Security Policy directive: "script-src 'self' 'report-sample'". Note that 'script-src-elem' was not explicitly set, so 'script-src' is used as a fallback.

If you see inline style errors, you need to add SHA-256 hashes / nonces to your CSP with RapidSec:

Refused to execute inline script because it violates the following Content Security Policy directive: "script-src 'self' 'report-sample'". Either the 'unsafe-inline' keyword, a hash ('sha256-RFWPLDbv2BY+rCkDzsE+0fr8ylGr2R2faWMhq4lfEQc='), or a nonce ('nonce-...') is required to enable inline execution.

If you see inline eval() errors, RapidSec will generate your CSP with the specific content of the errors:

Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self' 'report-sample'".

style-src/style-src-elem/style-src-attrviolations

Refused to load the stylesheet 'https://*.wp.com/c/*/wp-includes/css/dashicons.min.css' because it violates the following Content Security Policy directive: "style-src 'self' 'report-sample'". Note that 'style-src-elem' was not explicitly set, so 'style-src' is used as a fallback.

If you see inline style errors, you need to add SHA-256 hashes / nonces to your CSP with RapidSec:

Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self' 'report-sample'". Either the 'unsafe-inline' keyword, a hash ('sha256-RFWPLDbv2BY+rCkDzsE+0fr8ylGr2R2faWMhq4lfEQc='), or a nonce ('nonce-...') is required to enable inline execution.

font-srcviolations

Refused to load the font 'https://*.wp.com/c/*/wp-includes/fonts/dashicons.ttf?*' because it violates the following Content Security Policy directive: "font-src 'self'"

img-srcviolations

Refused to load the image 'wp.com' because it violates the following Content Security Policy directive: "img-src 'self'".

frame-srcviolations

[Report Only] Refused to frame 'wp.com' because it violates the following Content Security Policy directive: "frame-src 'self'".

form-actionviolations

[Report Only] Refused to send form data to 'wp.com' because it violates the following Content Security Policy directive: "form-action 'self'".

connect-srcviolations

[Report Only] Refused to connect to 'wp.com' because it violates the following Content Security Policy directive: "connect-src 'self'"