General plugins (Local): Content security policy

Maintained by Picture of Catalyst ITCatalyst IT, Picture of Brendan HeywoodBrendan Heywood
This plugin allows an admin to create a Custom Security Policy (CSP) in both reporting mode and enforcing mode. A simple use case is to detect and cleanup issues with non secure content after a migration from http to https, through to advanced policies to mitigate from XSS attacks.

Content security policy 2017041801

Release notes

Travis integration: Build Status


Why would you want this?

Security, security, security.

This plugin helps you to detect and eliminate security errors in your Moodle such as: - Mixed content (https/http) after you switched to HTTPS. - Same origin (or specified origin) policy for scripts and media data.

What is this?

This plugin enables Custom Security Policy headers across the Moodle website. Examples: - Report/enforce SSL origin for links, images etc. - Report/enforce same-origin for links, images etc.

How does it work?

Site admin configures CSP headers: Content-Security-Policy or Content-Security-Policy-Report-Only in the plugin settings. Header Content-Security-Policy-Report-Only is for recording CSP violations in Moodle and reviewing them later from the plugin's report page. Enabling of Content-Security-Policy blocks browser from showing site resources that violate defined rules.


Checkout or download the plugin source code into folder local\csp of your Moodle installation.

git clone local\csp


mkdir -p local/csp
unzip -d local/csp

Then go to your Moodle admin interface and complete installation and configuration. Example policy 'default-src https:;' will be reporting or enforcing the links to be HTTPS-only. Please note, the whole moodle website should be accessible via HTTPS for this to work. For more examples of other CSP directives please read here.


Relevant issue in Moodle Tracker: (

A complementary plugin which works by searching the moodle DB for bad links:

This plugin was developed by Catalyst IT Australia:

Catalyst IT

Moodle 2.9, 3.0, 3.1, 3.2

Version information

Version build number
Version release name
Stable version
MD5 Sum
Supported software
Moodle 2.9, Moodle 3.0, Moodle 3.1, Moodle 3.2

Version control information

Version control system (VCS)
VCS repository URL
VCS tag

Default installation instructions for plugins of the type General plugins (Local)

  1. Make sure you have all the required versions.
  2. Download and unpack the module.
  3. Place the folder in the "local" subdirectory.
  4. Visit to finish the installation.