Weston Ruter

<p>This plugin enforces a <a href="https://web.dev/articles/strict-csp" rel="nofollow ugc">Strict Content Security Policy</a> (CSP) on the frontend and login screen. This helps mitigate <a href="https://developer.mozilla.org/en-US/docs/Web/Security/Attacks/XSS" rel="nofollow ugc">cross-site scripting</a> (XSS) vulnerabilities. The policy cannot yet be applied to the WP Admin (see <a href="https://core.trac.wordpress.org/ticket/59446" rel="nofollow ugc">#59446</a>).</p>
<p>In <a href="https://core.trac.wordpress.org/ticket/58664" rel="nofollow ugc">#58664</a>, the manual construction of script tags was eliminated from <code>WP_Scripts</code> and inline scripts on frontend/login screen, thanks to the helper functions which had previously been introduced in <a href="https://core.trac.wordpress.org/ticket/39941" rel="nofollow ugc">#39941</a>.  This made it possible to apply Strict CSP, as long as themes and plugins are not directly printing <code><script></code> tags. Some bundled WordPress core themes <a href="https://github.com/search?q=repo%3AWordPress%2Fwordpress-develop+path%3A%2F%5Esrc%5C%2Fwp-content%5C%2Fthemes%5C%2F%2F+%2F%3Cscript%5B%5E%3E%5D*%3E%2F&type=code" rel="nofollow ugc">still do this</a> incorrectly (which has been reported in Trac as <a href="https://core.trac.wordpress.org/ticket/63806" rel="nofollow ugc">#63806</a>). For example, do not do this:</p>
<pre>function my_theme_supports_js() {
    echo '<script>document.body.classList.remove("no-js");</script>'; // ❌
}
add_action( 'wp_footer', 'my_theme_supports_js' );</pre>
<p>Instead, do this:</p>
<pre>function my_theme_supports_js() {
    wp_print_inline_script_tag( 'document.body.classList.remove("no-js");' ); // ✅
}
add_action( 'wp_footer', 'my_theme_supports_js' );</pre>
<p>So in order for scripts to execute, they must be printed using the relevant APIs in WordPress for adding scripts, including <a href="https://developer.wordpress.org/reference/functions/wp_enqueue_script/" rel="nofollow ugc"><code>wp_enqueue_script()</code></a>, <a href="https://developer.wordpress.org/reference/functions/wp_add_inline_script/" rel="nofollow ugc"><code>wp_add_inline_script()</code></a>, <a href="https://developer.wordpress.org/reference/functions/wp_localize_script/" rel="nofollow ugc"><code>wp_localize_script()</code></a>, <a href="https://developer.wordpress.org/reference/functions/wp_print_script_tag/" rel="nofollow ugc"><code>wp_print_script_tag()</code></a>, <a href="https://developer.wordpress.org/reference/functions/wp_print_inline_script_tag/" rel="nofollow ugc"><code>wp_print_inline_script_tag()</code></a>, and <a href="https://developer.wordpress.org/reference/functions/wp_enqueue_script_module/" rel="nofollow ugc"><code>wp_enqueue_script_module()</code></a>. Otherwise, a script’s execution will be blocked and an error will appear in the console, for example:</p>
<blockquote>
<p>Refused to execute inline script because it violates the following Content Security Policy directive: “script-src ‘nonce-9b539cfe47’ ‘unsafe-inline’ ‘strict-dynamic’ https: http:”. Note that ‘unsafe-inline’ is ignored if either a hash or nonce value is present in the source list.</p>
</blockquote>
<p>This also blocks scripts inside of <a href="https://developer.mozilla.org/en-US/docs/Web/HTML/Reference/Attributes#event_handler_attributes" rel="nofollow ugc">event handler attributes</a>, such as <code>onclick</code>, <code>onchange</code>, <code>onsubmit</code>, and <code>onload</code>. As noted on MDN:</p>
<blockquote>
<p>Warning: The use of event handler content attributes is discouraged. The mix of HTML and JavaScript often produces unmaintainable code, and the execution of event handler attributes may also be blocked by content security policies.</p>
</blockquote>
<p>This plugin also ensures that scripts added to the page from embeds (e.g. Tweets) also get the <code>nonce</code> attribute added.</p>


Strict CSP

Enforces a Strict Content Security Policy on the frontend and login screen to help mitigate any XSS vulnerabilities.

Hristo Pandjarov

Elena Chavdarova

Stoyan Georgiev

Stanimir Stoyanov

Ignat Georgiev

SiteGround

Asparuh Tenev

<p><strong>Bulletproof your website security in a few clicks against a range of security breaches, including brute-force attacks, malware threats and bots, with our free WordPress security plugin – Security Optimizer.</strong></p>
<p>Proactively monitor your site’s security to detect any suspicious activity and take immediate actions to protect your site and prevent further damage with these essential features:</p>
<ul>
<li>Enable <strong>2FA (Two-Factor Authentication)</strong> for an extra layer of website security</li>
<li>Set <strong>Limit Login Attempts</strong> to deter malicious login attempts and brute-force attacks</li>
<li>Change your default login URL to <strong>Custom Login URL</strong> to avoid attacks</li>
<li>Activate <strong>Advanced XSS Protection</strong> to fortify your website against malicious attacks</li>
<li><strong>Lock and Protect System Folders</strong> to ensure no unauthorized or malicious scripts can be executed in your system folders</li>
<li><strong>Disable Themes & Plugins Editor</strong> to safeguard your website from unauthorized access via the WordPress editor</li>
<li><strong>Hide WordPress Version</strong> effortlessly, keeping it hidden from prying eyes</li>
<li>Use <strong>Activity Log</strong> to monitor your site and quickly prevent malicious actions</li>
<li><strong>Post-Hack Actions</strong> to take immediate actions and prevent further damages</li>
</ul>
<p>Developed by the website security experts at <a href="https://www.siteground.com/wordpress-plugins/siteground-security" rel="nofollow ugc">SiteGround</a> and trusted by over 900,000 webmasters for its robust security shield and ease of use to safeguard WordPress applications from possible attacks on any hosting platform.</p>
<h4>AWARDS:</h4>
<p><a href="https://www.templatemonster.com/awards/winners-2022/" rel="nofollow ugc">Monster Awards 2022</a>: Best WordPress Security Plugin 🥇<br />
<a href="https://www.templatemonster.com/awards/winners-2021/" rel="nofollow ugc">Monster Awards 2021</a>: Best WordPress Security Plugin 🥇</p>
<h4>Plugin Video</h4>
<span class="embed-youtube" style="text-align:center; display: block;"><iframe loading="lazy" class="youtube-player" width="750" height="422" src="https://www.youtube.com/embed/FOheCz7sm9A?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"></iframe></span>
<h4>Plugin Tutorial</h4>
<p>Unveil the vast array of features and unleash the full potential of our security plugin in our <a href="https://www.siteground.com/tutorials/wordpress/sg-security/" rel="nofollow ugc">Security Optimizer Tutorial</a>.</p>
<h3>SITE PROTECTION FEATURES</h3>
<p>Safeguard your WordPress application using our powerful site security toolset. Our comprehensive features are specifically designed to strengthen your website’s defenses against malware, exploits, and various malicious activities. With these tools at your disposal, you can ensure the utmost bot, malware and brute force protection for your website:</p>
<h4>Lock and Protect System Folders</h4>
<p>Ensure the maximum security for your application’s system folders by preventing the execution of any unauthorized or malicious scripts. The Lock and Protect System Folders feature acts as a powerful shield against potential threats.</p>
<h4>Hide WordPress Version</h4>
<p>Protect your website from mass attacks by hiding the WordPress version, which helps to mitigate version-specific vulnerabilities.</p>
<h4>Disable Themes & Plugins Editor</h4>
<p>Enhance the security of your WordPress admin area by disabling the Themes & Plugins Editor, preventing potential coding errors and unauthorized access through the editor.</p>
<h4>Disable XML-RPC</h4>
<p>Mitigate potential security risks by disabling the XML-RPC protocol, which has been exploited in various attacks. Please note that disabling XML-RPC will restrict WordPress from communicating with third-party systems. We recommend enabling this feature unless you have a specific need for it.</p>
<h4>Disable RSS and ATOM Feeds</h4>
<p>Prevent content scraping and specific attacks on your site by disabling RSS and ATOM feeds. Unless you have readers accessing your site via RSS readers, it is recommended to keep this feature enabled.</p>
<h4>Advanced XSS Protection</h4>
<p>Add an extra layer of website security against cross-site scripting (XSS) attacks by enabling Advanced XSS Protection, bolstering the overall security of your website.</p>
<h4>Delete Default Readme.html</h4>
<p>Eliminate potential vulnerabilities by deleting the default readme.txt file, which contains information about your website. By removing this file, you reduce the risk of your site being listed in vulnerable sites targeted by hackers.</p>
<h3>Login Security</h3>
<h4>Custom Login Url</h4>
<p>Personalize your login URL to thwart potential attacks and create a strong entry point. Bid farewell to the default login URL and embrace a bespoke path of your choosing. Additionally, you have the freedom to modify the default sign-up URL as well.</p>
<h4>Login Access</h4>
<p>Restrict login page access to specific IP addresses or IP ranges, effectively thwarting malicious login attempts and deterring brute force attacks.</p>
<h4>2FA (Two-Factor Authentication)</h4>
<p>Immerse your website in an impenetrable shield of security with 2FA. This formidable feature demands that all admin users furnish a unique token, generated exclusively through the Google Authentication application, during the login process.</p>
<h4>Disable Common Usernames</h4>
<p>Don’t fall victim to predictable security breaches! The use of common usernames, such as ‘admin,’ poses a significant threat to the integrity of your website. Activate this option to disable the creation of common usernames. If any weak usernames already exist, we’ll prompt you to provide new, stronger alternatives.</p>
<h4>Limit Login Attempts</h4>
<p>Maintain control over unauthorized access attempts with Limit Login Attempts. Set a specific threshold for the number of login failures users can endure before consequences arise. After reaching the limit, the IP address associated with the unsuccessful login attempts will be blocked for one hour. Persistent failures will result in longer restrictions, starting with 24 hours and escalating to a week.</p>
<h3>ACTIVITY MONITORING</h3>
<p>Monitor your website and login page for unauthorized visitors and brute force attempts to prevent malicious actions</p>
<h4>Activity Log</h4>
<p>The Activity Log page provides you with a comprehensive view of the activities performed by registered, unknown, and blocked visitors. It allows you to closely monitor any suspicious behavior and take appropriate actions in case of a compromised user, plugin, or hacking attempt. You can leverage the quick tools available to swiftly block future attempts.</p>
<h4>Weekly Security Reports</h4>
<p>Receive a weekly traffic summary for your website directly to your inbox. This <strong>Weekly Security Report</strong> compiles data on both bot and human traffic, along with details about blocked login and visit attempts to proactively monitor traffic and promptly identify suspicious activity.</p>
<h3>POST-HACK ACTIONS</h3>
<p>Take immediate measures to protect your website if you suspect a compromise and prevent further damage. Here, you’ll find convenient solutions to address the situation effectively:</p>
<h4>Reinstall All Free Plugins</h4>
<p>In the event of a hack, utilizing the Reinstall All Free Plugins feature can help mitigate potential harm. This action reinstalls all of your free plugins, reducing the likelihood of additional exploits or the reuse of malicious code.</p>
<h4>Log Out All Users</h4>
<p>To prevent any further unauthorized activities by users or attackers, you can choose to log out all users instantly using the Log Out All Users feature.</p>
<h4>Force Password Reset</h4>
<p>By enforcing a password reset, you can ensure that all users are prompted to change their passwords during their next login. This not only strengthens the security of their accounts but also immediately logs out all currently logged-in users.</p>
<h3>Requirements</h3>
<ul>
<li>WordPress 4.7</li>
<li>PHP 7.0</li>
<li>Working .htaccess file</li>
</ul>
<h3>Data Collection</h3>
<p>Collection of technical data is optional and is <a href="https://www.siteground.com/kb/what-information-wp-plugins-collect" rel="nofollow ugc">listed here</a>. This data is collected only for technical analysis, improvements and the possibility to contact the plugin user in case urgent issues need to be fixed (for example a critical security release that needs to be communicated to site owners). The plugin user can manage their preferences within the WP admin to control the collection of technical data. We advise opting in for this data collection, as it can enhance the plugin’s performance. You may find more information on data collection in our <a href="https://www.siteground.com/viewtos/siteground_plugins_privacy_notice" rel="nofollow ugc">Plugins Privacy Notice</a>.</p>


Security Optimizer – The All-In-One Protection Plugin

Yesterday I started researching a new security plugin that I could switch to for all my WordPress sites (about 50). Skimming the plugin directory I found SiteGround Security and I must say this is the most promising looking plugin I have ever encountered!

The biggest PRO for me: SiteGround is a professional hosting service and they are using this plugin on all WordPress sites they host, so they will have a strong motivation to keep sg-security as high-quality as possible, without the need to upsell it like so many other plugins are doing it.

I have two questions: 

1. Is there a place where you host the plugin's source publicly, like for example on GitHub? I couldn't find anything except a security warning about 2FA in an earlier version (1.2.5, can't post link here due to WP guidelines).

2. What was your reasoning behind not making the limit_login_attempts periods (1 hour, 1 day, 1 week) un-filterable? I wanted to immediately reduce the first period to something like 20 minutes, but those periods are hard-coded right now inside SG_Security\Login_Service\Login_Service->log_login_attempt( $error ) (Version 1.3.7).

Thanks again.

Wow!


Llevo decenas de webs de clientes y he encontrado muchas webs infectadas con plugins de seguridad premium. 



Tras instalar el plugin de seguridad de SiteGround y un buen cortafuegos nunca más he tenido problemas en ninguna web.


Sencillo y efectivo, mejor que el resto


Cannot unsubscribe from the emails without admin access. In my experience, this makes the plugin extremely annoying. They do not plan to fix this.


Cannot unsubscribe from the emails

Secure your WordPress site from brute-force attacks, threats, malware, and bots. Free to use and easy to set up.

Strict CSP vs Security Optimizer – The All-In-One Protection Plugin