Fixed: Content Security Policy Warnings in Magento 2
CSP, i.e., Content Security Policy is a robust tool introduced to prevent attacks on your Magento 2 store that aims to offer an additional layer of defence to detect and fight against Cross-Site Scripting (XSS) and related attacks, including card skimmers, session hijacking, clickjacking, and more. As of version Magento 2.3.5, it supports CSP headers and provides ways to configure them.
One can disable Magento 2 content security policy also. However, disabling CSP results in more possibilities of attacks on the store. Instead of blocking all third-party APIs completely, you can use the below solution and allow your selected third-party API as per your requirement.
CSP is implemented in Magento 2.3.5 with an aim to offer an additional layer of defence to detect and mitigate cross-site scripting and its related data injection attacks.
Method to Fix Content Security Policy Warnings in Magento 2:
You can use this solution to solve the warning shown below:
1. Create a csp_whitelist.xml file in Vendor\Extension\etc
|
1 2 3 4 5 6 7 8 9 10 11 12 |
<? xml version = "1.0"?> <csp_whitelist xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Csp/etc/csp_whitelist.xsd"> <policies> <policy id="script-src"> <values> <value id="uniqueId" type="host">https://domain.com</value> <value id="uniqueId" type="host">accounts.google.com</value> </values> </policy> </policies> </csp_whitelist> |
You can add a domain to the whitelist for a policy like script-src, style-src, font-src and others by adding a csp_whitelist.xml to your custom module’s etc folder.
We have to pass a unique random id to the value field.
In the value tag, enter the domain which is mentioned in the warning.
2. Create a config.xml file in Vendor\Extension\etc
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 |
<?xml version="1.0"?> <config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:module:Magento_Store:etc/config.xsd"> <default> <csp> <mode> <storefront> <report_only>0</report_only> </storefront> <admin> <report_only>0</report_only> </admin> </mode> </csp> </default> </config> |
Content Security Policy works in two modes:
- report – only – Magento reports the policy violations but does not act upon it. It is mainly used for debugging. CSP works in this mode by default.
- restrict mode – Magento acts in the case of policy violations.
Here, we will use the default mode with zero value.
It’s an example of ‘script-src’ warning, you can use the below solution for such kind of similar warnings as per the above path and method.
- style-src:
123456<policy id="style-src"><values><value id="uniqueId" type="host">https://domain.com</value><value id="uniqueId" type="host">https://accounts.google.com/gsi/style</value></values></policy> - frame-src:
123456<policy id="frame-src"><values><value id="uniqueId" type="host">https://domain.com</value><value id="uniqueId" type="host">https://accounts.google.com</value></values></policy> - connect-src:
123456<policy id="connect-src"><values><value id="uniqueId" type="host">https://domain.com</value><value id="uniqueId" type="host">https://accounts.google.com/gsi/status</value></values></policy> - img-src:
123456<policy id="img-src"><values><value id="uniqueId" type="host">https://domain.com</value><value id="meetanshi-image" type="host">https://meetanshi.com/media.png</value></values></policy> - font-src:
123456<policy id="font-src"><values><value id="uniqueId" type="host">https://domain.com</value><value id="uniqueId" type="host">*.gstatic.com</value></values></policy>
You can solve any kind of CSP warning by following the above method.
Ways to Add Whitelisted Resources to Custom Code
The following table describes each type of CSP to configure it for your custom code/extension/theme
|
CSP Code & Description |
|
|---|---|
| CSP Code | Description |
| default-src | The default policy. |
| base-url | Defines which URLs can appear in a page’s <base> element. |
| child-src | Defines the sources for workers and embedded frame contents. |
| connect-src | Defines the sources that can be loaded using script interfaces. |
| font-src | Defines which sources can serve fonts. |
| form-action | Defines valid endpoints for submission from |
| frame-ancestors | Defines the sources that can embed the current page. |
| img-src | Defines the sources from which images can be loaded. |
| manifest-src | Defines the allowable contents of web app manifests. |
| media-src | Defines the sources from which images can be loaded. |
| object-src | Defines the sources for the |
That’s it.
Any doubts? If so, mention them in the Comments section below for me to help you out asap.
Do share your thoughts on Magento CSP in the Comments section below.
Also, I’d be grateful if you can help me spread the word about the post among Magento Community via social media.
Thank You!
Still need help? Hire our Adobe-certified Magento experts.
![Magento 2.3.3: Know Everything about [October 2019] Release](https://meetanshi.com/blog/wp-content/uploads/2019/10/Magento-2.3.3-Know-Everything-about-October-2019-Release.png)
8 Comments
Hi, how do I remove “The source list for the Content Security Policy directive ‘frame-src’ contains an invalid source: ‘data:text’. It will be ignored.” it’s blocking my google map to be rendered.
Hey Alex,
Please have a look in blog at section: frame-src:
you have to add map link in xml file.
Hii
How to fix The Content-Security-Policy directive ‘frame-ancestors’ does not support the source expression ”unsafe-inline”
also The Content Security Policy directive ‘report-uri’ specifies as endpoint ”. This endpoint will be ignored since it violates the policy for Mixed Content.
Hello Harish
0
Use the below code in etc/config.xml file
Thank You
Hi,
How do I bite “The Content-Security-Policy directive ‘frame-ancestors’ does not support the source expression ”unsafe-inline”
jquery-3.1.1.min.js:3 ” when I’m logged in the admin panel?
Pawel
Hello Pawel,
Use the below code in etc/config.xml file
<admin>
<frame-ancestors>
<inline>0</inline> </frame-ancestors> </admin> Thank You
So where should we these files to? I didnt see a VendorExtension path?
Hello Steve,
VendorExtension resides in app/code.
for example Meetanshi_Csp is a extension inside app/code directory
so for us vendor = Meetanshi and Extension = Csp
Thank You.