[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fBln0Tfo-g6ZZ8N6XwqzflIPJVK1g1cVWBoCXJCb9Xpg":3},{"slug":4,"name":5,"version":6,"author":7,"author_profile":8,"description":9,"short_description":10,"active_installs":11,"downloaded":12,"rating":13,"num_ratings":14,"last_updated":15,"tested_up_to":16,"requires_at_least":17,"requires_php":18,"tags":19,"homepage":24,"download_link":25,"security_score":26,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29,"vulnerabilities":30,"developer":31,"crawl_stats":28,"alternatives":36,"analysis":140,"fingerprints":396},"sea-sp-community-edition","SeaSP Community Edition","1.8.3","bluetriangle","https:\u002F\u002Fprofiles.wordpress.org\u002Fbluetriangle\u002F","\u003Cp>SeaSP Community Edition is an automated \u003Cstrong>Content Security Policy Manager\u003C\u002Fstrong>. SeaSP allows you to create, configure, manage, and deploy a Content Security Policy for your site.\u003C\u002Fp>\n\u003Cp>The WordPress SeaSP Community Edition plugin catalogs the domains that appear on your site. Categorize and filter out unwanted domains. Add a layer of WordPress security site from Magecart and other cross-site scripting attacks to keep your WordPress site safe.\u003C\u002Fp>\n\u003Cp>SeaSP installs a strict non-blocking CSP to collect violation data and provide a violation report. Violation data flows into the WordPress database as a PHP option within the plugin options schema. Violations can be approved by domains and categorized by directives (CSS, fonts, images, JS, etc.). You can also approve base domains and subdomains. The SeaSP UI helps users by explaining what each directive does, and how to use them to create a CSP.\u003C\u002Fp>\n\u003Cp>After configuring the domain and directive settings switch the CSP to blocking mode. Once the CSP goes into blocking mode, the site’s protected from any unrecognized code. SeaSP Community Edition helps secure your site.\u003C\u002Fp>\n\u003Ch3>Upgrade Notice for 1.4 only\u003C\u002Fh3>\n\u003Cul>\n\u003Cli>When you install this version you will need to rebuild your CSP\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>Once installed, a strict non-blocking report-only CSP is implemented on your site. Visit each page of your site to collect CSP violations.\u003Cbr \u002F>\nVisit the Current Violations page of the plugin to review domains that have violated a directive in the CSP.\u003Cbr \u002F>\nReview each of the domains carefully and check for misspellings of common domains like adobee.com instead of adobe.com as this is a common way hackers inject content into your site.\u003Cbr \u002F>\nIf you feel confident that the domain belongs on your site and it should be serving the file type stated, click the toggle to approve the domain to include it in the CSP.\u003Cbr \u002F>\nIf you want to allow subdomains of that domain to be able to serve that type of content, click the Manage subdomains button to view the subdomains.\u003Cbr \u002F>\nAfter this process, you might still see CSP violations regarding inline scripts, inline styles, blobs, or data.\u003Cbr \u002F>\nTo allow these this type of content in the community version you must navigate to the Directive Settings page, find the offending directive, then toggle the appropriate option.\u003Cbr \u002F>\nFor convenience, each option has a tooltip explaining what it allows in your CSP.\u003C\u002Fp>\n\u003Ch3>Walk Through\u003C\u002Fh3>\n\u003Cp>A walk through video can be found on YouTube \u003Ca href=\"https:\u002F\u002Fyoutu.be\u002FXdJNh6LEKJw\" rel=\"nofollow ugc\">here\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cspan class=\"embed-youtube\" style=\"text-align:center; display: block;\">\u003Ciframe loading=\"lazy\" class=\"youtube-player\" width=\"750\" height=\"422\" src=\"https:\u002F\u002Fwww.youtube.com\u002Fembed\u002FXdJNh6LEKJw?version=3&rel=1&showsearch=0&showinfo=1&iv_load_policy=1&fs=1&hl=en-US&autohide=2&wmode=transparent\" allowfullscreen=\"true\" style=\"border:0;\" sandbox=\"allow-scripts allow-same-origin allow-popups allow-presentation allow-popups-to-escape-sandbox\">\u003C\u002Fiframe>\u003C\u002Fspan>\u003C\u002Fp>\n\u003Ch3>Contributing\u003C\u002Fh3>\n\u003Cp>Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.\u003Cbr \u002F>\nThis project has been tested on WordPress up to version 5.8 on both single and multi-site instances.\u003Cbr \u002F>\nThe project can be found on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fblue-triangle-tech\u002Fsea-sp-community-edition\" rel=\"nofollow ugc\">github\u003C\u002Fa>.\u003Cbr \u002F>\nThis project is sponsored by \u003Ca href=\"www.bluetriangle.com\" rel=\"nofollow ugc\">Blue Triangle\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch3>Third Party Libraries\u003C\u002Fh3>\n\u003Cp>We use \u003Ca href=\"https:\u002F\u002Fgetbootstrap.com\u002F\" rel=\"nofollow ugc\">Bootstrap\u003C\u002Fa> for the UI of our plugin to make the interface clean and simple.\u003Cbr \u002F>\nBootstraps license can be found \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Ftwbs\u002Fbootstrap\u002Fblob\u002Fmain\u002FLICENSE\" rel=\"nofollow ugc\">here\u003C\u002Fa>\u003C\u002Fp>\n\u003Cp>We use \u003Ca href=\"https:\u002F\u002Fwww.bootstraptoggle.com\u002F\" rel=\"nofollow ugc\">bootstrap toggle\u003C\u002Fa> because simple check boxes can be confusing and we wanted our CSP mangers UI to feel easy. This code was developed for The New York Times by \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fminhur\" rel=\"nofollow ugc\">Min Hur\u003C\u002Fa> and is licensed under \u003Ca href=\"https:\u002F\u002Fopensource.org\u002Flicenses\u002FMIT\" rel=\"nofollow ugc\">MIT\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>License\u003C\u002Fh3>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fchoosealicense.com\u002Flicenses\u002Fgpl-3.0\u002F\" rel=\"nofollow ugc\">GNU\u003C\u002Fa>\u003C\u002Fp>\n\u003Ch3>Opt In usage data collection\u003C\u002Fh3>\n\u003Cp>As of version 1.5 users will be able to opt-in for data collection to help us determine how many people are using our plugin and what features we should be working on in future version. This can be managed in the Usage Data Settings page. We collect and send the following data:\u003Cbr \u002F>\n1. wordpress version\u003Cbr \u002F>\n2. wordpress debug mode\u003Cbr \u002F>\n3. wordpress multisite\u003Cbr \u002F>\n4. the base url that the plugin is on ex; www.bluetriangle.com\u003Cbr \u002F>\nThis data is only accessible to the Blue Triangle organization and will be used to determine our user base and feature planning.\u003C\u002Fp>\n","SeaSP Community Edition is an automated Content Security Policy Manager. SeaSP allows you to create, configure, manage, and deploy a Content Security  …",20,4225,94,3,"2021-07-19T19:09:00.000Z","5.8.13","5.1","7.0",[20,21,22,23],"content-security-policy","csp","http-headers","security","https:\u002F\u002Fbluetrianglemarketing.github.io\u002FSeaSP-Community-Edition\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fsea-sp-community-edition.1.8.3.zip",85,0,null,"2026-03-15T15:16:48.613Z",[],{"slug":7,"display_name":7,"profile_url":8,"plugin_count":32,"total_installs":11,"avg_security_score":26,"avg_patch_time_days":33,"trust_score":34,"computed_at":35},1,30,84,"2026-04-04T05:40:36.083Z",[37,62,81,104,124],{"slug":22,"name":38,"version":39,"author":40,"author_profile":41,"description":42,"short_description":43,"active_installs":44,"downloaded":45,"rating":46,"num_ratings":47,"last_updated":48,"tested_up_to":49,"requires_at_least":50,"requires_php":51,"tags":52,"homepage":57,"download_link":58,"security_score":59,"vuln_count":60,"unpatched_count":27,"last_vuln_date":61,"fetched_at":29},"HTTP Headers","1.19.2","Dimitar Ivanov","https:\u002F\u002Fprofiles.wordpress.org\u002Fzinoui\u002F","\u003Cp>HTTP Headers gives your control over the http headers returned by your blog or website.\u003C\u002Fp>\n\u003Cp>Headers supported by HTTP Headers includes:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Access-Control-Allow-Origin\u003C\u002Fli>\n\u003Cli>Access-Control-Allow-Credentials\u003C\u002Fli>\n\u003Cli>Access-Control-Max-Age\u003C\u002Fli>\n\u003Cli>Access-Control-Allow-Methods\u003C\u002Fli>\n\u003Cli>Access-Control-Allow-Headers\u003C\u002Fli>\n\u003Cli>Access-Control-Expose-Headers\u003C\u002Fli>\n\u003Cli>Age \u003C\u002Fli>\n\u003Cli>Content-Security-Policy\u003C\u002Fli>\n\u003Cli>Content-Security-Policy-Report-Only\u003C\u002Fli>\n\u003Cli>Cache-Control\u003C\u002Fli>\n\u003Cli>Clear-Site-Data\u003C\u002Fli>\n\u003Cli>Connection\u003C\u002Fli>\n\u003Cli>Content-Encoding\u003C\u002Fli>\n\u003Cli>Content-Type\u003C\u002Fli>\n\u003Cli>Cross-Origin-Embedder-Policy\u003C\u002Fli>\n\u003Cli>Cross-Origin-Opener-Policy\u003C\u002Fli>\n\u003Cli>Cross-Origin-Resource-Policy\u003C\u002Fli>\n\u003Cli>Expect-CT\u003C\u002Fli>\n\u003Cli>Expires\u003C\u002Fli>\n\u003Cli>Feature-Policy\u003C\u002Fli>\n\u003Cli>NEL\u003C\u002Fli>\n\u003Cli>Permissions-Policy\u003C\u002Fli>\n\u003Cli>Pragma\u003C\u002Fli>\n\u003Cli>P3P\u003C\u002Fli>\n\u003Cli>Referrer-Policy\u003C\u002Fli>\n\u003Cli>Report-To\u003C\u002Fli>\n\u003Cli>Strict-Transport-Security\u003C\u002Fli>\n\u003Cli>Timing-Allow-Origin\u003C\u002Fli>\n\u003Cli>Vary\u003C\u002Fli>\n\u003Cli>WWW-Authenticate\u003C\u002Fli>\n\u003Cli>X-Content-Type-Options\u003C\u002Fli>\n\u003Cli>X-DNS-Prefetch-Control\u003C\u002Fli>\n\u003Cli>X-Download-Options\u003C\u002Fli>\n\u003Cli>X-Frame-Options\u003C\u002Fli>\n\u003Cli>X-Permitted-Cross-Domain-Policies\u003C\u002Fli>\n\u003Cli>X-Powered-By\u003C\u002Fli>\n\u003Cli>X-Robots-Tag\u003C\u002Fli>\n\u003Cli>X-UA-Compatible\u003C\u002Fli>\n\u003Cli>X-XSS-Protection\u003C\u002Fli>\n\u003C\u002Ful>\n","HTTP Headers adds CORS & security HTTP headers to your website.",50000,715994,86,70,"2024-12-22T11:49:00.000Z","6.7.5","3.2","5.3",[53,54,55,22,56],"cors-headers","csp-header","custom-headers","security-headers","https:\u002F\u002Fgithub.com\u002Friverside\u002Fhttp-headers","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fhttp-headers.1.19.2.zip",91,4,"2023-07-13 00:00:00",{"slug":63,"name":64,"version":65,"author":66,"author_profile":67,"description":68,"short_description":69,"active_installs":70,"downloaded":71,"rating":46,"num_ratings":72,"last_updated":73,"tested_up_to":74,"requires_at_least":75,"requires_php":76,"tags":77,"homepage":79,"download_link":80,"security_score":26,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"csp-manager","Content Security Policy Manager","1.2.1","Patrick Sletvold","https:\u002F\u002Fprofiles.wordpress.org\u002F16patsle\u002F","\u003Cp>\u003Cstrong>Content Security Policy Manager\u003C\u002Fstrong> is a WordPress plugin that allows you to easily configure \u003Ca href=\"https:\u002F\u002Fdeveloper.mozilla.org\u002Fen-US\u002Fdocs\u002FWeb\u002FHTTP\u002FCSP\" rel=\"nofollow ugc\">Content Security Policy headers\u003C\u002Fa> for your site. You can have different CSP headers for the admin interface, the frontend for logged in users, and the frontend for regular visitors. The CSP directives can be individually enabled, and each policy can be set to enforce, report or be disabled.\u003C\u002Fp>\n\u003Cp>Please note that this plugin offers limited help in figuring out what the contents of the policy should be. It only lets you configure the CSP in a easy to use interface.\u003C\u002Fp>\n","Plugin for configuring Content Security Policy headers for your site. Allows different CSP headers for admin, logged inn frontend and regular visitors",2000,33739,6,"2022-08-09T17:33:00.000Z","6.1.10","4.6","7.2",[20,21,23,56,78],"xss","","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcsp-manager.1.2.1.zip",{"slug":82,"name":83,"version":84,"author":85,"author_profile":86,"description":87,"short_description":88,"active_installs":89,"downloaded":90,"rating":91,"num_ratings":92,"last_updated":93,"tested_up_to":94,"requires_at_least":95,"requires_php":96,"tags":97,"homepage":100,"download_link":101,"security_score":59,"vuln_count":102,"unpatched_count":27,"last_vuln_date":103,"fetched_at":29},"gd-security-headers","GD Security Headers","1.8","Milan Petrovic","https:\u002F\u002Fprofiles.wordpress.org\u002Fgdragon\u002F","\u003Cp>Configure various security-related HTTP headers, including Content Security Policy, Feature Policy, Referrer Policy and more. For CSP and XSS plugin supports report logging with 2 additional database tables to store reports from browsers.\u003C\u002Fp>\n\u003Ch4>Supported security headers\u003C\u002Fh4>\n\u003Cp>The plugin has support for the following HTTP headers:\u003C\u002Fp>\n\u003Cul>\n\u003Cli>Content Security Policy (CSP) – with reporting\u003C\u002Fli>\n\u003Cli>XSS Protection (XXP) – with reporting\u003C\u002Fli>\n\u003Cli>Feature Policy (Permissions Policy)\u003C\u002Fli>\n\u003Cli>Content Type – No Sniff Policy\u003C\u002Fli>\n\u003Cli>Strict Transport Security\u003C\u002Fli>\n\u003Cli>Referrer Policy\u003C\u002Fli>\n\u003Cli>Frame Options\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>For CSP, the plugin allows you to set rules for all currently supported directives, additional settings including setting the policy in Report or Live mode. The plugin also includes special extensions that can automatically fill CSP rules for popular Google services you might be using on your website (Fonts, Maps, Adsense, Analytics, TagManager and more) and other popular services (Gravatar, Instagram, PayPal Vimeo and more).\u003C\u002Fp>\n\u003Cp>And, for Feature Policy (or Permissions Policy), the plugin allows you to set rules for all currently supported rules (over 25 rules, supported by different browsers).\u003C\u002Fp>\n\u003Ch4>FLoC \u002F Browsing Topics\u003C\u002Fh4>\n\u003Cp>Permissions Policy rules list includes ‘browsing-topics’ rule that can be used to disable Google’s new tracking method ‘Browsing Topics API’ (which replaced ‘Federated Learning of Cohorts’ or ‘FLoC’).\u003C\u002Fp>\n\u003Ch4>Methods for adding headers\u003C\u002Fh4>\n\u003Cp>The plugin can add all the generated headers into HTACCESS file (for Apache web servers), and they will be applied to all files, not just WordPress generated content. If your website is not using Apache (or .HTACCESS), all rules are generated with each page request and will work with any server type.\u003C\u002Fp>\n\u003Cp>And, if you don’t use Apache web server, the plugin has a panel where it displays generated headers for most popular servers: Apache, Nginx and IIS, and you can copy generated headers to add to server configuration files.\u003C\u002Fp>\n\u003Ch4>About the plugin\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>More information about \u003Ca href=\"https:\u002F\u002Fplugins.dev4press.com\u002Fgd-security-headers\u002F\" rel=\"nofollow ugc\">GD Security Headers\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>Support and Knowledge Base for \u003Ca href=\"https:\u002F\u002Fsupport.dev4press.com\u002Fkb\u002Fproduct\u002Fgd-security-headers\u002F\" rel=\"nofollow ugc\">GD Security Headers\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n","Configure various security-related HTTP headers, including CSP, XSS, Referrer Policy and more.",1000,30187,80,8,"2024-06-07T08:16:00.000Z","6.6.5","5.5","7.4",[20,21,98,99,23],"dev4press","permission-policy","https:\u002F\u002Fplugins.dev4press.com\u002Fgd-security-headers\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fgd-security-headers.zip",2,"2023-10-29 00:00:00",{"slug":105,"name":106,"version":107,"author":108,"author_profile":109,"description":110,"short_description":111,"active_installs":112,"downloaded":113,"rating":114,"num_ratings":115,"last_updated":116,"tested_up_to":117,"requires_at_least":118,"requires_php":96,"tags":119,"homepage":122,"download_link":123,"security_score":114,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"no-unsafe-inline","No unsafe-inline","1.3.0","Giuseppe","https:\u002F\u002Fprofiles.wordpress.org\u002Fmociofiletto\u002F","\u003Cp>Content Security Policy (CSP) is a computer security standard introduced to prevent cross-site scripting (XSS), clickjacking and other code injection attacks resulting from execution of malicious content in the trusted web page context.\u003Cbr \u002F>\nCross-site scripting (XSS) is a type of security vulnerability that can be found in some web applications.\u003Cbr \u002F>\nXSS attacks enable attackers to inject client-side scripts into web pages viewed by other users.\u003Cbr \u002F>\nA cross-site scripting vulnerability may be used by attackers to bypass access controls like the same-origin policy.\u003Cbr \u002F>\nLooking at National Vulnerability Database run by US NIST, \u003Cem>more than 1100 (November 2025) vulnerabilities\u003C\u002Fem> are reported as \u003Ca href=\"https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fsearch#\u002Fnvd\u002Fhome?vulnRevisionStatusList=published&keyword=XSS%20Wordpress&resultType=records\" rel=\"nofollow ugc\">XSS for WordPress’ plugins and themes\u003C\u002Fa>.\u003C\u002Fp>\n\u003Cp>\u003Cem>Keeping your site up-to-date\u003C\u002Fem> with the latest versions of plugins and themes is the \u003Cstrong>first\u003C\u002Fstrong> line of defense to ensure your site’s security.\u003C\u002Fp>\n\u003Cp>The second thing to do, is to \u003Cstrong>deploy a strict Content Security Policy\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Ch3>The main problem\u003C\u002Fh3>\n\u003Cp>The main problem with Content Security Policies implemented in the real world is that \u003Ca href=\"https:\u002F\u002Fresearch.google\u002Fpubs\u002Fpub45542\u002F\" rel=\"nofollow ugc\">they are too weak to really protect your site\u003C\u002Fa> and that many of them can be trivially bypassed by an attacker.\u003C\u002Fp>\n\u003Ch3>The proposed solution\u003C\u002Fh3>\n\u003Cp>Google researchers recommend, instead of whole host whitelisting, to activate individual scripts via a CSP nonces approach.\u003Cbr \u002F>\nIn addition, in order to facilitate the adoption of nonce-based CSP, they proposed the ’strict-dynamic’ keyword.\u003C\u002Fp>\n\u003Ch3>The problem(s) with CSP in WordPress\u003C\u002Fh3>\n\u003Col>\n\u003Cli>\n\u003Cp>Manual creation of a policy\u003C\u002Fp>\n\u003Cp>Usually, a WordPress project is a mix of code written by different authors who contributed to the Core and or wrote plugins and themes.\u003Cbr \u002F>\nIf it is possible to whitelist every external script loaded from a \u003Ccode>\u003Cscript src=\"\">\u003C\u002Fcode>, the real truth is that in a WordPress project you can have dozens of those scripts included with your plugins and calculate a cryptographic hash for each of them to be included in your CSP header can be a frustrating job. However, there are many browser extensions and WordPress’ plugins that can help you in this job.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Inline scripts\u003C\u002Fp>\n\u003Cp>WordPress core, and plugins, use inline scripts. For these scripts, you can compute hashes to be inserted manually into your policy, only if these scripts do not change at any page load. Unfortunately, this is not very common, as it is frequent to include variable values calculated server side in inline scripts. And it means that your inline scripts change too frequently to manually add their hashes to your policy.\u003Cbr \u002F>\nThis commonly happens when scripts are \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FWordPress\u002FWordPress\u002Fblob\u002Fa793be201b9c23dbe8b90a6ecd53ab52336f0f91\u002Fwp-includes\u002Fscript-loader.php#L636\" rel=\"nofollow ugc\">“localized”\u003C\u002Fa>.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>WordPress has no API to implement nonces for CSP\u003C\u002Fp>\n\u003Cp>Even if it is easy to generate a nonce for each page view, this nonce has to be inserted in every script tag used to embed inline scripts in your page as\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Cscript nonce=\"rAnd0m\">\n    doWhatever();\n\u003C\u002Fscript>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>and in your script-src directive:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>script-src 'nonce-rAnd0m';\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>And, of course, a nonce must be unique for each HTTP response.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>Unsafe hashes \u002F Inline styles\u003C\u002Fp>\n\u003Cp>Sometimes, HTML elements as images or buttons use HTML Event Attributes (onclick, onsubmit…) to let events trigger actions in a browser.\u003Cbr \u002F>\nYou cannot use hashes or nonces for script included in event attributes and, adopting a strict CSP, requires refactoring those patterns into safer alternatives or to use ‘unsafe-hashes’.\u003Cbr \u002F>\nYou got a similar problem when inline styles are used in HTML tags:\u003C\u002Fp>\n\u003Cpre>\u003Ccode>\u003Ch1 style=\"color:blue;text-align:center;\">This is a heading\u003C\u002Fh1>\n\u003Cp style=\"color:red;\">This is a paragraph.\u003C\u002Fp>\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>CSP Level 2 browsers may be ok with just putting the hash in your style-src directive. However, to allow hashes in the style attribute on inline CSS on browsers that support CSP Level 3, you may get an error like this\u003C\u002Fp>\n\u003Cpre>\u003Ccode>    Refused to apply inline style because it violates the following Content Security Policy directive: \"style-src 'self' 'sha256-nMxMqdZhkHxz5vAuW\u002FPAoLvECzzsmeAxD\u002FBNwG15HuA='\". Either the 'unsafe-inline' keyword, a hash ('sha256-nMxMqdZhkHxz5vAuW\u002FPAoLvECzzsmeAxD\u002FBNwG15HuA='), or a nonce ('nonce-...') is required to enable inline execution.\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>To allow inline styles you need to use ‘unsafe-hashes’ in your style-src directive (that is, in facts, unsafe).\u003Cbr \u002F>\n^\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Ch3>This plugin approach\u003C\u002Fh3>\n\u003Cp>This plugin affords those problems in this way:\u003C\u002Fp>\n\u003Col>\n\u003Cli>During a capture phase, it detects the scripts, styles and other embedded content present in the pages of your site and stores them in the database.\u003C\u002Fli>\n\u003Cli>Then you have to whitelist these contents from plugin admin.\u003C\u002Fli>\n\u003Cli>The plugin uses machine learning to cluster inline scripts trying to aggregate scripts generated by the same server side (PHP) code. So, you can authorize one script example to authorize all scripts that the classifier predicts to label as whitelisted clusters.\u003C\u002Fli>\n\u003Cli>You can choose to use hashes to authorize external scripts (and the plugin will allow you to include Subresource Integrity in your \u003Ccode>\u003Cscript>\u003C\u002Fcode> and \u003Ccode>\u003Clink>\u003C\u002Fcode>)\u003C\u002Fli>\n\u003Cli>You can use hashes or nonces to authorize inline scripts.\u003C\u002Fli>\n\u003Cli>You can ask the plugin to refactor your page to not use event attributes (converted in a inline script) and inline styles (converted in an internal CSS).\u003C\u002Fli>\n\u003Cli>You can set one or more violations’ report endpoints.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>The plugin supports multisite installations and has (too) many options documented in inline help.\u003C\u002Fp>\n\u003Ch3>Creating a Content Security Policy\u003C\u002Fh3>\n\u003Cp>After plugin activation, go to Settings menu and search for CSP Settings submenu.\u003Cbr \u002F>\nThe steps you are supposed to do are the following.\u003C\u002Fp>\n\u003Col>\n\u003Cli>From the Tools tab, activate the capture of the tags and use your site by visiting all the pages or having your users visit them for a long time long period based on the use of your site (hours or days).\u003C\u002Fli>\n\u003Cli>From the Tools tab, perform the data clustering in the database (it can use many server resources).\u003C\u002Fli>\n\u003Cli>Go to the Base rules tab and include in the CSP directives the desired values ​​(help you with the table at the bottom of the page).\u003C\u002Fli>\n\u003Cli>Go to the external scripts tab, inline scripts tab and scripts invoked by event handlers tab and authorize the execution of all the legitimate scripts present on the pages of your site.\u003C\u002Fli>\n\u003Cli>Leaving the tag capture active, activate the policy test (at this stage the plugin will generate some violations of the temporary policy used to record additional values to be included in the directives of your “content security policy”).\u003C\u002Fli>\n\u003Cli>After visiting again your site pages, disable the capture of the tags and repeat the previous steps 2, 3 and 4.\u003C\u002Fli>\n\u003Cli>Enable site protection.\u003C\u002Fli>\n\u003C\u002Fol>\n\u003Cp>N.B. When you update plugins or themes, if something doesn’t work properly on your site pages, temporarily deactivate the protection and repeat steps 1 to 7.\u003C\u002Fp>\n\u003Ch3>Plugin hooks\u003C\u002Fh3>\n\u003Ch4>Filters\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline\u002Fblob\u002Fd068711d56c2d7b228b524f640f5e13af3327097\u002Fpublic\u002Fclass-no-unsafe-inline-public.php#L419\" rel=\"nofollow ugc\">nunil_output_csp_headers_header_csp\u003C\u002Fa>\u003Cbr \u002F>\nnunil_output_csp_headers_header_csp is available since version 1.2.3 and can be used to modify the Content-Security-Policy header before it is sent to browser\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline\u002Fblob\u002Fd068711d56c2d7b228b524f640f5e13af3327097\u002Fsrc\u002FNunil_Manipulate_DOM.php#L930\" rel=\"nofollow ugc\">no_unsafe_inline_not_sri_sources\u003C\u002Fa>\u003Cbr \u002F>\nno_unsafe_inline_not_sri_sources can be used to modify the list of external resources that do not support SRI (Subresource Integrity)\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline\u002Fblob\u002Fd068711d56c2d7b228b524f640f5e13af3327097\u002Fmu-plugin\u002Fno-unsafe-inline-output-buffering.php#L100\" rel=\"nofollow ugc\">no_unsafe_inline_final_output\u003C\u002Fa>\u003Cbr \u002F>\nno_unsafe_inline_final_output is an internal filter used to manipulate the output of the WordPress process just before the output is sent to the browser.\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline\u002Fblob\u002Fd068711d56c2d7b228b524f640f5e13af3327097\u002Fmu-plugin\u002Fno-unsafe-inline-output-buffering.php#L107\" rel=\"nofollow ugc\">no_unsafe_inline_meta_injector\u003C\u002Fa>\u003Cbr \u002F>\nno_unsafe_inline_meta_injector is an internal filter hook used to inject meta http-equiv=”Content-Security-Policy” if variable is set\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch4>Actions\u003C\u002Fh4>\n\u003Cul>\n\u003Cli>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline\u002Fblob\u002Fd068711d56c2d7b228b524f640f5e13af3327097\u002Fincludes\u002Fclass-no-unsafe-inline.php#L213-L217\" rel=\"nofollow ugc\">nunil_upgrade\u003C\u002Fa> Functions hooked on nunil_upgrade will run when the plugin is upgraded\u003C\u002Fp>\n\u003C\u002Fli>\n\u003Cli>\n\u003Cp>\u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline\u002Fblob\u002Fd068711d56c2d7b228b524f640f5e13af3327097\u002Fincludes\u002Fclass-no-unsafe-inline.php#L254\" rel=\"nofollow ugc\">nunil_output_csp_headers\u003C\u002Fa> Functions hooked to nunil_output_csp_headers will run when the plugin output the CSP HTTP response header\u003C\u002Fp>\n\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch3>Code and libraries\u003C\u002Fh3>\n\u003Cp>This version of the plugin uses:\u003Cbr \u002F>\n* to parse HTML:\u003Cbr \u002F>\n  * \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fivopetkov\u002Fhtml5-dom-document-php\" rel=\"nofollow ugc\">ivopetkov\u002FHTML5DOMDocument\u003C\u002Fa> on PHP\u003C8.4 and libxml\u003C=2.13.09\u003Cbr \u002F>\n  * \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMasterminds\u002Fhtml5-php\" rel=\"nofollow ugc\">Masterminds\\HTML5\u003C\u002Fa> on PHP\u003C8.4 and libxml>2.13.09\u003Cbr \u002F>\n  * \u003Ca href=\"https:\u002F\u002Fwww.php.net\u002Fmanual\u002Fen\u002Fmigration84.new-features.php#migration84.new-features.dom\" rel=\"nofollow ugc\">\\Dom\\HTMLDocument\u003C\u002Fa>: The new ext-dom features with HTML5 support on PHP>8.4\u003Cbr \u002F>\n* \u003Ca href=\"https:\u002F\u002Frubixml.com\u002F\" rel=\"nofollow ugc\">RubixML\u003C\u002Fa> for machine learning \u003Cstrong>\u003Cem>from version 1.1.0\u003C\u002Fem>\u003C\u002Fstrong> – \u003Cem>\u003Ca href=\"https:\u002F\u002Fphp-ml.readthedocs.io\u002Fen\u002Flatest\u002F\" rel=\"nofollow ugc\">PHP-ML\u003C\u002Fa> was used in versions 1.0.x\u003C\u002Fem>;\u003Cbr \u002F>\n* \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fopctim\u002Fphp-nilsimsa\" rel=\"nofollow ugc\">opctim\u002Fphp-nilsimsa\u003C\u002Fa> to calculate and compare Nilsimsa digests.\u003C\u002Fp>\n\u003Cp>The log functions have been taken from\u003Cbr \u002F>\n* \u003Ca href=\"https:\u002F\u002Fgithub.com\u002Fperfectyorg\u002Fperfecty-push-wp\" rel=\"nofollow ugc\">perfectyorg\u002Fperfecty-push-wp\u003C\u002Fa>, \u003Cstrong>\u003Cem>something you should \u003Ca href=\"https:\u002F\u002Fwordpress.org\u002Fplugins\u002Fperfecty-push-notifications\u002F\" rel=\"ugc\">really try\u003C\u002Fa> if you want to implement web Push notifications in your site.\u003C\u002Fem>\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cp>The \u003Cstrong>complete list of dependencies\u003C\u002Fstrong> used in this plugin can be seen in \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline\u002Fnetwork\u002Fdependencies\" rel=\"nofollow ugc\">dependency graph\u003C\u002Fa> on GitHub.\u003C\u002Fp>\n\u003Ch3>Contributions, Issues, Bugs\u003C\u002Fh3>\n\u003Cp>Plugin code is hosted on a public repository on \u003Ca href=\"https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline\" rel=\"nofollow ugc\">GitHub\u003C\u002Fa>.\u003Cbr \u002F>\nReach me over there to help and suggest.\u003C\u002Fp>\n","No unsafe-inline helps you to build a Content Security Policy avoiding to use 'unsafe-inline' and 'unsafe-hashes'.",200,11184,100,5,"2025-12-04T21:50:00.000Z","6.9.4","5.9",[20,21,120,23,121],"multisite","unsafe-inline","https:\u002F\u002Fgithub.com\u002FMocioF\u002FNo-unsafe-inline","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fno-unsafe-inline.1.3.0.zip",{"slug":125,"name":126,"version":127,"author":128,"author_profile":129,"description":130,"short_description":131,"active_installs":114,"downloaded":132,"rating":47,"num_ratings":60,"last_updated":133,"tested_up_to":117,"requires_at_least":118,"requires_php":134,"tags":135,"homepage":138,"download_link":139,"security_score":114,"vuln_count":27,"unpatched_count":27,"last_vuln_date":28,"fetched_at":29},"csp-antsst","CSP Friendly Security","1.5.2","Pascal CESCATO","https:\u002F\u002Fprofiles.wordpress.org\u002Fpcescato\u002F","\u003Cp>Adds a CSP header compatible with most WP plugins without breaking styles.\u003C\u002Fp>\n","Adds a CSP header compatible with most WP plugins without breaking styles.",2755,"2026-01-01T13:42:00.000Z","7.3",[20,21,136,56,137],"nonces","sha256-hashes","https:\u002F\u002Ftsw.ovh\u002F","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fcsp-antsst.1.5.2.zip",{"attackSurface":141,"codeSignals":211,"taintFlows":350,"riskAssessment":388,"analyzedAt":395},{"hooks":142,"ajaxHandlers":173,"restRoutes":205,"shortcodes":206,"cronEvents":207,"entryPointCount":210,"unprotectedCount":27},[143,149,153,157,161,165,169],{"type":144,"name":145,"callback":146,"file":147,"line":148},"action","activated_plugin","Blue_Triangle_Automated_CSP_Free_redirect","Bluetriangle-free-csp.php",513,{"type":144,"name":150,"callback":151,"file":147,"line":152},"send_headers","Blue_Triangle_Automated_CSP_Free_Inject_CSP",548,{"type":144,"name":154,"callback":155,"file":147,"line":156},"wp_head","Blue_Triangle_Automated_CSP_Free_Inject_Tag",562,{"type":144,"name":158,"callback":159,"file":147,"line":160},"admin_menu","Blue_Triangle_Automated_CSP_Free_themes_page",625,{"type":144,"name":162,"callback":163,"file":147,"line":164},"admin_notices","Blue_Triangle_Automated_CSP_Free_Violations_Notice",1022,{"type":144,"name":166,"callback":167,"file":147,"line":168},"Blue_Triangle_Automated_CSP_Free_Cron_Update","Blue_Triangle_Automated_CSP_Free_Cron_Job",1066,{"type":144,"name":170,"callback":171,"file":147,"line":172},"plugins_loaded","Blue_Triangle_Automated_CSP_Free_update_db_check",1135,[174,179,182,185,188,191,194,197,200,203],{"action":175,"nopriv":176,"callback":175,"hasNonce":177,"hasCapCheck":176,"file":178,"line":102},"Blue_Triangle_Automated_CSP_Free_Approve_SUBDOMAIN",false,true,"src\\controllers\\Ajax.php",{"action":180,"nopriv":176,"callback":180,"hasNonce":177,"hasCapCheck":176,"file":178,"line":181},"Blue_Triangle_Automated_CSP_Free_SUBDOMAIN_TABLE",53,{"action":183,"nopriv":176,"callback":183,"hasNonce":177,"hasCapCheck":176,"file":178,"line":184},"Blue_Triangle_Automated_CSP_Free_Csp_Mode",154,{"action":186,"nopriv":176,"callback":186,"hasNonce":177,"hasCapCheck":176,"file":178,"line":187},"Blue_Triangle_Automated_CSP_Free_Csp_Usage_Update",173,{"action":189,"nopriv":176,"callback":189,"hasNonce":177,"hasCapCheck":176,"file":178,"line":190},"Blue_Triangle_Automated_CSP_Free_Csp_Delay",219,{"action":192,"nopriv":176,"callback":192,"hasNonce":177,"hasCapCheck":176,"file":178,"line":193},"Blue_Triangle_Automated_CSP_Free_Csp_Error_Mode",236,{"action":195,"nopriv":176,"callback":195,"hasNonce":177,"hasCapCheck":176,"file":178,"line":196},"Blue_Triangle_Automated_CSP_Free_Approve",253,{"action":198,"nopriv":176,"callback":198,"hasNonce":177,"hasCapCheck":176,"file":178,"line":199},"Blue_Triangle_Automated_CSP_Free_Directive_Options",307,{"action":201,"nopriv":176,"callback":201,"hasNonce":177,"hasCapCheck":176,"file":178,"line":202},"Blue_Triangle_Automated_CSP_Free_Send_CSP",392,{"action":201,"nopriv":177,"callback":201,"hasNonce":177,"hasCapCheck":176,"file":178,"line":204},393,[],[],[208],{"hook":166,"callback":166,"file":147,"line":209},1027,10,{"dangerousFunctions":212,"sqlUsage":213,"outputEscaping":252,"fileOperations":27,"externalRequests":102,"nonceChecks":348,"capabilityChecks":60,"bundledLibraries":349},[],{"prepared":214,"raw":215,"locations":216},63,17,[217,220,222,224,226,228,230,232,234,236,238,240,242,244,246,248,250],{"file":147,"line":218,"context":219},530,"$wpdb->query() with variable interpolation",{"file":147,"line":221,"context":219},531,{"file":147,"line":223,"context":219},532,{"file":147,"line":225,"context":219},533,{"file":147,"line":227,"context":219},534,{"file":147,"line":229,"context":219},535,{"file":147,"line":231,"context":219},536,{"file":147,"line":233,"context":219},537,{"file":147,"line":235,"context":219},538,{"file":147,"line":237,"context":219},1086,{"file":147,"line":239,"context":219},1123,{"file":147,"line":241,"context":219},1124,{"file":147,"line":243,"context":219},1125,{"file":147,"line":245,"context":219},1126,{"file":147,"line":247,"context":219},1127,{"file":147,"line":249,"context":219},1128,{"file":147,"line":251,"context":219},1129,{"escaped":253,"rawEcho":254,"locations":255},23,49,[256,259,261,262,264,266,269,271,273,275,277,279,281,283,285,287,288,290,292,294,296,298,300,302,304,306,308,310,313,316,318,319,320,321,322,323,324,325,327,329,332,334,336,338,340,342,343,344,346],{"file":147,"line":257,"context":258},594,"raw output",{"file":147,"line":260,"context":258},995,{"file":147,"line":89,"context":258},{"file":147,"line":263,"context":258},1005,{"file":147,"line":265,"context":258},1010,{"file":267,"line":268,"context":258},"src\\views\\dashboard-view.php",12,{"file":267,"line":270,"context":258},15,{"file":267,"line":272,"context":258},18,{"file":267,"line":274,"context":258},21,{"file":267,"line":276,"context":258},24,{"file":267,"line":278,"context":258},27,{"file":267,"line":280,"context":258},39,{"file":267,"line":282,"context":258},43,{"file":267,"line":284,"context":258},61,{"file":267,"line":286,"context":258},75,{"file":267,"line":59,"context":258},{"file":267,"line":289,"context":258},96,{"file":267,"line":291,"context":258},108,{"file":267,"line":293,"context":258},116,{"file":267,"line":295,"context":258},128,{"file":267,"line":297,"context":258},138,{"file":267,"line":299,"context":258},148,{"file":267,"line":301,"context":258},158,{"file":267,"line":303,"context":258},175,{"file":267,"line":305,"context":258},185,{"file":267,"line":307,"context":258},195,{"file":267,"line":309,"context":258},205,{"file":311,"line":312,"context":258},"src\\views\\directives-view.php",168,{"file":314,"line":315,"context":258},"src\\views\\general-view.php",135,{"file":317,"line":268,"context":258},"src\\views\\help-view.php",{"file":317,"line":270,"context":258},{"file":317,"line":272,"context":258},{"file":317,"line":274,"context":258},{"file":317,"line":276,"context":258},{"file":317,"line":278,"context":258},{"file":317,"line":280,"context":258},{"file":317,"line":282,"context":258},{"file":317,"line":326,"context":258},58,{"file":328,"line":291,"context":258},"src\\views\\usage-view.php",{"file":330,"line":331,"context":258},"src\\views\\violations-view.php",22,{"file":330,"line":333,"context":258},25,{"file":330,"line":335,"context":258},28,{"file":330,"line":337,"context":258},31,{"file":330,"line":339,"context":258},34,{"file":330,"line":341,"context":258},37,{"file":330,"line":254,"context":258},{"file":330,"line":181,"context":258},{"file":330,"line":345,"context":258},68,{"file":330,"line":347,"context":258},152,9,[],[351,369,377],{"entryPoint":352,"graph":353,"unsanitizedCount":27,"severity":368},"Blue_Triangle_Automated_CSP_Free_Approve (src\\controllers\\Ajax.php:254)",{"nodes":354,"edges":366},[355,360],{"id":356,"type":357,"label":358,"file":178,"line":359},"n0","source","$_REQUEST",278,{"id":361,"type":362,"label":363,"file":178,"line":364,"wp_function":365},"n1","sink","query() [SQLi]",299,"query",[367],{"from":356,"to":361,"sanitized":177},"low",{"entryPoint":370,"graph":371,"unsanitizedCount":27,"severity":368},"\u003CAjax> (src\\controllers\\Ajax.php:0)",{"nodes":372,"edges":375},[373,374],{"id":356,"type":357,"label":358,"file":178,"line":359},{"id":361,"type":362,"label":363,"file":178,"line":364,"wp_function":365},[376],{"from":356,"to":361,"sanitized":177},{"entryPoint":378,"graph":379,"unsanitizedCount":27,"severity":368},"\u003Cusage-view> (src\\views\\usage-view.php:0)",{"nodes":380,"edges":386},[381,383],{"id":356,"type":357,"label":382,"file":328,"line":34},"$_SERVER",{"id":361,"type":362,"label":384,"file":328,"line":291,"wp_function":385},"echo() [XSS]","echo",[387],{"from":356,"to":361,"sanitized":177},{"summary":389,"deductions":390},"The \"sea-sp-community-edition\" v1.8.3 plugin exhibits a generally positive security posture with several key strengths. The static analysis reveals a complete absence of unprotected entry points across AJAX handlers, REST API routes, and shortcodes, which is an excellent foundation for security. The plugin also avoids dangerous functions and file operations, further reducing potential attack vectors. Furthermore, the vulnerability history is clean, with no known CVEs, indicating a potentially stable and well-maintained codebase over time.\n\nHowever, there are areas for improvement. While the majority of SQL queries use prepared statements, the 21% that do not could pose a risk of SQL injection if these queries involve user-supplied input without proper sanitization. The most significant concern arises from the low rate of properly escaped output (32%). This indicates a high likelihood of Cross-Site Scripting (XSS) vulnerabilities, as untrusted data could be rendered directly in the browser without sufficient encoding. The presence of external HTTP requests, while not inherently a vulnerability, warrants careful review to ensure they are made to trusted sources and handle responses securely.\n\nIn conclusion, \"sea-sp-community-edition\" v1.8.3 is built on a strong security framework with robust access control on its entry points and a clean vulnerability history. The primary weakness lies in its insufficient output escaping, creating a notable risk of XSS attacks. Addressing this specific issue and carefully reviewing the unescaped SQL queries would significantly enhance the plugin's security.",[391,393],{"reason":392,"points":270},"Low rate of proper output escaping",{"reason":394,"points":115},"SQL queries not using prepared statements","2026-03-16T22:59:56.120Z",{"wat":397,"direct":420},{"assetPaths":398,"generatorPatterns":408,"scriptPaths":409,"versionParams":410},[399,400,401,402,403,404,405,406,407],"\u002Fwp-content\u002Fplugins\u002Fsea-sp-community-edition\u002Fassets\u002Fcss\u002Fmain.css","\u002Fwp-content\u002Fplugins\u002Fsea-sp-community-edition\u002Fassets\u002Fcss\u002Freport.css","\u002Fwp-content\u002Fplugins\u002Fsea-sp-community-edition\u002Fassets\u002Fcss\u002Fsettings.css","\u002Fwp-content\u002Fplugins\u002Fsea-sp-community-edition\u002Fassets\u002Fjs\u002FCSP.js","\u002Fwp-content\u002Fplugins\u002Fsea-sp-community-edition\u002Fassets\u002Fjs\u002FCSP_API.js","\u002Fwp-content\u002Fplugins\u002Fsea-sp-community-edition\u002Fassets\u002Fjs\u002FCSP_Settings.js","\u002Fwp-content\u002Fplugins\u002Fsea-sp-community-edition\u002Fassets\u002Fjs\u002Fmain.js","\u002Fwp-content\u002Fplugins\u002Fsea-sp-community-edition\u002Fassets\u002Fjs\u002Freports.js","\u002Fwp-content\u002Fplugins\u002Fsea-sp-community-edition\u002Fassets\u002Fjs\u002Fscripts.js",[],[402,403,404,405,406,407],[411,412,413,414,415,416,417,418,419],"sea-sp-community-edition\u002Fassets\u002Fcss\u002Fmain.css?ver=","sea-sp-community-edition\u002Fassets\u002Fcss\u002Freport.css?ver=","sea-sp-community-edition\u002Fassets\u002Fcss\u002Fsettings.css?ver=","sea-sp-community-edition\u002Fassets\u002Fjs\u002FCSP.js?ver=","sea-sp-community-edition\u002Fassets\u002Fjs\u002FCSP_API.js?ver=","sea-sp-community-edition\u002Fassets\u002Fjs\u002FCSP_Settings.js?ver=","sea-sp-community-edition\u002Fassets\u002Fjs\u002Fmain.js?ver=","sea-sp-community-edition\u002Fassets\u002Fjs\u002Freports.js?ver=","sea-sp-community-edition\u002Fassets\u002Fjs\u002Fscripts.js?ver=",{"cssClasses":421,"htmlComments":428,"htmlAttributes":434,"restEndpoints":437,"jsGlobals":441,"shortcodeOutput":445},[422,423,424,425,426,427],"seasp_report_container","seasp_settings_container","seasp-directive-row","seasp-directive-input","seasp-plugin-settings-table","seasp-log-table",[429,430,431,432,433],"\u003C!-- Generated by Sea SP Community Edition -->","\u003C!-- Begin Sea SP Settings -->","\u003C!-- End Sea SP Settings -->","\u003C!-- Begin Sea SP Reports -->","\u003C!-- End Sea SP Reports -->",[435,436],"data-seasp-directive","data-seasp-option",[438,439,440],"\u002Fwp-json\u002Fseaspc\u002Fv1\u002Fsettings","\u002Fwp-json\u002Fseaspc\u002Fv1\u002Freports","\u002Fwp-json\u002Fseaspc\u002Fv1\u002Fcsp-data",[442,443,444],"seaspConfig","seaspReports","seaspSettings",[446,447],"[seasp_reports]","[seasp_settings]"]