Weston Ruter

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>).
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:
<pre>function my_theme_supports_js() {
 echo '<script>document.body.classList.remove("no-js");</script>'; // ❌
}
add_action( 'wp_footer', 'my_theme_supports_js' );</pre>
Instead, do this:
<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>
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:
<blockquote>
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.
</blockquote>
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:
<blockquote>
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.
</blockquote>
This plugin also ensures that scripts added to the page from embeds (e.g. Tweets) also get the <code>nonce</code> attribute added.

Strict CSP

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

jp-secure

You can find docs, FAQ and more detailed information on <a href="https://www.jp-secure.com/siteguard_wp_plugin_en/" rel="nofollow ugc">English Page</a> <a href="https://www.jp-secure.com/siteguard_wp_plugin/" rel="nofollow ugc">Japanese Page</a>.
Simply install the SiteGuard WP Plugin, WordPress security is improved. 
This plugin is a security plugin that specializes in the login attack of brute force, such as protection and management capabilities.
Notes
<ul>
<li>It does not support the multisite function of WordPress.</li>
<li>It only supports Apache 1.3, 2.x for Web servers.</li>
<li>To use the CAPTCHA function, the expansion library “mbstring” and “gd” should be installed on php.</li>
<li>To use the management page filter function and login page change function, “mod_rewrite” should be loaded on Apache.</li>
<li>To use the WAF Tuning Support, WAF ( SiteGuard Server Edition ) should be installed on Apache.</li>
</ul>
There are the following functions.
<ul>
<li>Admin Page IP Filter</li>
</ul>
It is the function for the protection against the attack to the management page (under wp-admin.) 
To the access from the connection source IP address which does not login to the management page, 404 (Not Found) is returned. 
At the login, the connection source IP address is recorded and the access to that page is allowed. 
The connection source IP address which does not login for more than 24 hours is sequentially deleted. 
The URL (under wp-admin) where this function is excluded can be specified.
<ul>
<li>Rename Login</li>
</ul>
It is the function to decrease the vulnerability against an illegal login attempt attack such as a brute force attack or a password list attack. 
The login page name (wp-login.php) is changed. The initial value is “login_<5 random digits>” but it can be changed to a favorite name.
<ul>
<li>CAPTCHA</li>
</ul>
It is the function to decrease the vulnerability against an illegal login attempt attack such as a brute force attack or a password list attack, 
or to receive less comment spam. For the character of CAPTCHA, hiragana and alphanumeric characters can be selected.
<ul>
<li>Login Lock</li>
</ul>
It is the function to decrease the vulnerability against an illegal login attempt attack such as a brute force attack or a password list attack. 
Especially, it is the function to prevent an automated attack. The connection source IP address the number of login failure of which reaches 
the specified number within the specified period is blocked for the specified time. 
Each user account is not locked.
<ul>
<li>Login Alert</li>
</ul>
It is the function to make it easier to notice unauthorized login. E-mail will be sent to a login user when logged in. 
If you receive an e-mail to there is no logged-in idea, please suspect unauthorized login.
<ul>
<li>Fail Once</li>
</ul>
It is the function to decrease the vulnerability against a password list attack. Even is the login input is correct, the first login must fail. 
After 5 seconds and later within 60 seconds, another correct login input make login succeed. At the first login failure, the following error message is displayed.
<ul>
<li>Disable Pingback</li>
</ul>
The pingback function is disabled and its abuse is prevented.
<ul>
<li>Block Author Query</li>
</ul>
Prevents leakage of user names due to “/?author=” access.
<ul>
<li>Updates Notify</li>
</ul>
Basic of security is that always you use the latest version. If WordPress core, plugins, and themes updates are needed , sends email to notify administrators.
<ul>
<li>WAF Tuning Support</li>
</ul>
It is the function to create the rule to avoid the false detection in WordPress (including 403 error occurrence with normal access,) 
if WAF ( SiteGuard Server Edition ) by EG Secure Solutions is installed on a Web server. WAF prevents the attack from the outside against the Web server, 
but for some WordPress or plugin functions, WAF may detect the attack which is actually not attack and block the function. 
By creating the WAF exclude rule, the WAF protection function can be activated while the false detection for the specified function is prevented.
<h4>Translate</h4>
If you have created your own language pack, or have an update of an existing one, you can send <a href="https://codex.wordpress.org/Translating_WordPress" rel="nofollow ugc">gettext PO and MO files</a> to sgdev@jp-secure.com so that We can bundle it into SiteGuard WP Plugin. You can download the latest <a href="https://plugins.svn.wordpress.org/siteguard/trunk/languages/siteguard.pot" rel="nofollow ugc">POT file</a>, and <a href="https://plugins.svn.wordpress.org/siteguard/branches/languages/" rel="nofollow ugc">PO files in each language</a>.

SiteGuard WP Plugin


誰でもユーザーを登録できるサイトを作っているのですが、ログイン保護機能を利用しています。スパムアカウントが減りました。


ログイン保護に利用しています

SiteGurad WP Plugin is the plugin specialized for the protection against the attack to the management page and login.

Strict CSP vs SiteGuard WP Plugin