Store Prose

<p>A lightweight WordPress security plugin to prevent brute force attacks and disable XML-RPC.</p>
<h3>What can you do with WordShield?</h3>
<ul>
<li>Brute Force Protection</li>
<li>Disable XML-RPC API exploits</li>
<li>Change default Login URL  –<strong>Planned</strong></li>
<li>Add Security Headers –<strong>Planned</strong></li>
<li>Content Protection –<strong>Planned</strong></li>
<li>Login Security –<strong>Planned</strong></li>
<li>Hide Generator Tags</li>
<li>Disable PHP Editing</li>
</ul>
<h3>Future Roadmap</h3>
<ul>
<li>Stop user enumerations.</li>
<li>Request rate throttler.</li>
<li>Prevent comment spam.</li>
<li>IP Ban.</li>
<li>Prevent code execution.</li>
<li>2FA</li>
<li>Backup & Restore.</li>
<li>Support for multisite.</li>
<li>Logs, Notifications, and more!</li>
</ul>
<h3>Note:</h3>
<p>The current version of the WordShield Security plugin does not work in a multisite environment.</p>
<h3>Advantages of WordShield Security Plugin</h3>
<ul>
<li><strong>Lean Code—</strong> Unlike most other Security Plugins, WordShield focuses on the core functionalities and has zero bloat.</li>
<li><strong>Ultrafast—</strong> This lightweight plugin adds negligible overhead to your website. Each new release is tested for performance before making it available for general use. </li>
<li>It added only 0.004 seconds of execution time in our internal performance profiling tests.*</li>
<li><strong>Failsafe—</strong> This WordPress security plugin does not modify any core file. It does not alter the .htaccess file as well. With easy-to-use recovery options, you can be sure that your WordPress website <strong>will never break</strong>.</li>
<li><strong>Best Practices—</strong> WordShield follows WordPress best practices and respects the coding standards.</li>
<li><strong>Maintenance & Support—</strong> WordShield has a planned roadmap for the future. It is well-supported and updated for compatibility with each WordPress upgrade.</li>
</ul>
<h3>How to Limit Login Attempts in WordPress?</h3>
<p>You can limit login attempts to your WordPress website using the WordShield security plugin. You can prevent Brute Force attacks with the following steps:</p>
<ul>
<li>Open the settings screen after installing and activating the plugin.</li>
<li>Navigate to the Brute Force tab on the settings screen.</li>
<li>Set the maximum number of invalid attempts you want to allow for each user.</li>
<li>Set the time (in minutes) you want to lock a user account after exceeding the maximum number of invalid attempts.</li>
<li>If you do not want to prevent Brute Force attacks, select 0 for both of these settings.</li>
<li>Save the settings.</li>
</ul>
<p>👉 The WordShield security plugin informs the user about the remaining retries before the account becomes locked.<br />
👉 If an account gets locked, WordShield informs the user about the time to wait before trying to log in again.<br />
👉 You can customize the default error messages in any language by keying in the message in the 2 optional fields.<br />
👉 Use %%MINUTES_LEFT%% to show the time in minutes in your custom message. Use %%ATTEMPTS_LEFT%% to show the number of retries left in your custom message.</p>
<h3>How to disable XML-RPC API exploits?</h3>
<p>XML-RPC is enabled by default in every WordPress installation. While XML-RPC is necessary for certain services and plugins like Jetpack, it can make websites vulnerable to remote code injection.</p>
<p>You can protect your website from the XML-RPC vulnerability as follows:</p>
<ul>
<li>Open the settings screen after installing and activating the plugin.</li>
<li>Navigate to the XML-RPC tab on the settings screen.</li>
<li>Check the Disable XML-RPC checkbox to disable XML-RPC completely.</li>
<li>If you are using JetPack, you can select the Enable Jetpack access so that the Jetpack plugin continues to work seamlessly.</li>
<li>If you need specific IPs to access XML-RPC API, key in the comma-separated list of IPs in the Whitelisted IPs field.</li>
<li>Save the settings.</li>
</ul>
<h3>How to Hide the Generator tags in WordPress?</h3>
<p>WordPress and WooCommerce generator tags let the potential attackers can easily identify the specific version of WordPress (or WooCommerce) you are using. This, in turn, exposes technical vulnerabilities thereby making your site more susceptible to hacking attempts.</p>
<p>You can hide the generator tags in WordPress by the following steps.</p>
<ul>
<li>Open the settings screen after installing and activating the plugin.</li>
<li>Navigate to the Extras tab on the settings screen.</li>
<li>Select the checkbox Remove Generator tags.</li>
<li>Save the settings.</li>
</ul>
<h3>How to disable PHP editing?</h3>
<p>You can disable PHP editing to prevent accidental changes in plugins and themes causing a complete system crash.</p>
<p>You can disable PHP editing with the following steps:</p>
<ul>
<li>Open the settings screen after installing and activating the plugin.</li>
<li>Navigate to the Extras tab on the settings screen.</li>
<li>Select the checkbox Disable PHP editing.</li>
<li>Select the checkbox Disable theme change if you want to hide the Appearance menu as well.</li>
<li>Save the settings.</li>
</ul>


WordPress Security Plugin – WordShield

A lightweight WordPress security plugin to prevent brute force attacks and disable XML-RPC.

brainvireinfo

<p>You can now disable XML-RPC to avoid Brute force attack for given IPs or can even enable access for some IPs. XML-RPC on WordPress is actually an API that gives developers who build mobile apps, desktop apps and other services, the ability to talk to a WordPress site. The XML-RPC API that WordPress provides gives developers, a way to write applications (for you) that can do many of the things that you can do when logged into WordPress via the web interface.</p>
<h4>Features</h4>
<p>Block XML-RPC by following way.</p>
<ul>
<li>Disable pingback.ping, pingback.extensions.getPingbacks and Unset X-Pingback from HTTP headers, that will block bots to access specified method.</li>
<li>Disable/Block XML-RPC for all users.</li>
</ul>


Manage XML-RPC

Enable/Disable XML-RPC for all or based on IP list, also you can control pingback and Unset X-Pingback from HTTP headers.

WordPress Security Plugin – WordShield vs Manage XML-RPC