Enrico Sorcinelli

JSON REST API and XML-RPC API are powerful ways to remotely interact with WordPress.
If you don’t have external applications that need to communicate with your WordPress instance using JSON REST API or XML-RPC API you should disable access to them for external requests.
In the standard WordPress installation JSON REST API and XML-RPC API are enabled by default. 
In particular the REST API is turned on also for unlogged users. This means that your WordPress instance is potentially leaking data, for example anyone could be able to:
<ul>
<li>copy easily your published contents natively with the REST API (and not with a web crawler);</li>
<li>get the list of all users (with their ID, nickname and name);</li>
<li>retrieve other information that you didn’t want to be public (such as an unlisted published page or a saved media not yet used).</li>
</ul>
Even if you could do the stuff by writing your own code using native filters, this plugin aims to help you to control JSON REST API and XML-RPC API accesses from the administration panel or programmatically by a simple API filter.
<h3>Basic Features</h3>
<ul>
<li>Disable REST API interface for unlogged users.</li>
<li>Disable JSONP support on REST API.</li>
<li>Add Basic Authentication to REST API.</li>
<li>Remove REST <code><link></code> tags, REST <code>Link</code> HTTP header and REST Really Simple Discovery (RSD) informations.</li>
<li>Setup trusted users, IP/Networks and endpoints for unlogged users REST requests.</li>
<li>Change REST endpoint prefix.</li>
<li>Disable XML-RPC API interface.</li>
<li>Remove <code><link></code> to the Really Simple Discovery (RDS) informations.</li>
<li>Remove <code>X-Pingback</code> HTTP header.</li>
<li>Setup trusted users, IP/Networks and methods for XML-RPC requests.</li>
<li>Show user’s access informations in users list administration screen.</li>
</ul>
<h3>Usage</h3>
Once the plugin is installed you can control settings in the following ways:
<ul>
<li>Using the Settings->REST XML-RPC Data Checker administration screen.</li>
<li>Programmatically, by using <code>rest_xmlrpc_data_checker_settings</code> filter (see below).</li>
</ul>
<h3>API</h3>
<h4>Hooks</h4>
<code>rest_xmlrpc_data_checker_settings</code>
Filters plugin settings values.
<pre><code>apply_filters( 'rest_xmlrpc_data_checker_settings', array $settings )
</code></pre>
<code>rest_xmlrpc_data_checker_admin_settings</code>
Filter allowing to display or not the plugin settings page in the administration.
<pre><code>apply_filters( 'rest_xmlrpc_data_checker_admin_settings', boolean $display )
</code></pre>
<code>rest_xmlrpc_data_checker_rest_error</code>
Filter JSON REST authentication error after plugin checks.
<pre><code>apply_filters( 'rest_xmlrpc_data_checker_rest_error', WP_Error|boolean $result )
</code></pre>
<code>xmlrpc_before_insert_post</code>
Filter XML-RPC post data to be inserted via XML-RPC before to insert post into database.
<pre><code>apply_filters( 'xmlrpc_before_insert_post', array|IXR_Error $content_struct, WP_User $user )
</code></pre>

REST XML-RPC Data Checker

REST XML-RPC Data Checker allow to check JSON REST and XML-RPC API requests and grant access permissions.

WebProtect.ai

Ananda Krishna

Shikhil

WP Hardening is a tool which performs a real-time security audit of your website to find missing security best practices. Using our ‘Security Fixer’ you can also fix these with a single click from your WordPress backend.

<h3>Discontinuation Notice</h3>
IMPORTANT: This plugin is discontinued
This is to inform you that this plugin is no longer being maintained or updated. We have placed a discontinuation request with the WordPress team, and the plugin will soon be ‘closed’ for new installations.
This plugin was launched as a side project and has sadly reached the end of its journey. Thank you for your understanding and for using our plugin. We apologize for any inconvenience this may cause.
What This Means for You
<ol>
<li>No Further Updates: There will be no more updates, bug fixes, or new features.</li>
<li>No Support: Support for this plugin is no longer available.</li>
</ol>
We recommend that you deactivate and delete this plugin from your WordPress site as soon as possible. Please seek alternative plugins to replace the functionality provided by this plugin.
<h3>Features</h3>
<h3>Hardening Audit</h3>
<ol>
<li>WordPress Version Check 
 It checks if your website is on the latest version or not.
 </li>
<li>Checking Outdated Plugins 
 It checks if your website is running the updated plugins or not.
 </li>
<li>Checking PHP Version 
 WP Hardening also checks if your website is running on a secure version of PHP.
 </li>
<li>Checking File & Folder Permissions 
 WP Hardening also checks if your website is built on the secured version of PHP or not.
 </li>
<li>Database Password Strength 
 We check the strength of passwords used on your database. Not having a secured password can become an easy target for Brute-Force attacks.
 </li>
<li>Checking Firewall Protection 
 We’ll check if your website is being protected by a firewall or not. Firewalls leverage a great monitoring and filtering system on your website.
 </li>
</ol>
<h3>Security Fixers</h3>
Admin & API Security
<ol>
<li>Stop User Enumeration Hackers & bad bots can easily find usernames in WordPress by visiting URLs like yourwebsite.com/?author=1. This can significantly help them in performing larger attacks like Bruteforce & SQL injection.</li>
<li>Change Login URL Prevent admin password brute-forcing by changing the URL for the wp-admin login area. You can change the url only when this fixer is disabled.</li>
<li>Disable XMLRPC XMLRPC is often targeted by bots to perform brute force & DDoS attacks (via pingback) causing considerable stress on your server. However, there are some services which rely on xmlrpc. Be sure you definitely do not need xmlrpc before disabling it.</li>
<li>Disable WP API JSON Since 4.4 version, WordPress added JSON REST API which largely benefits developers. However, it’s often targeted for bruteforce attacks just like in the case of xmlrpc. If you are not using it, best is to disable it.</li>
<li>Disable File Editor If a hacker is able to get access to your WordPress admin, with the file editor enabled it becomes quite easy for them to add malicious code to your theme or plugins. If you are not using this, it’s best to keep the file editor disabled.</li>
<li>Disable WordPress Application Passwords WordPress application passwords have full permissions of the user that generated them, making it possible for an attacker to gain control of a website by tricking the site administrator into granting permission to their malicious application.</li>
</ol>
Disable Information Disclosure & Remove Meta information
<ol>
<li>Hide WordPress version number 
 This gives away your WordPress version number making life of a hacker simple as they’ll be able to find targeted exploits for your WordPress version. It’s best to keep this hidden, enabling the button shall do that.
 </li>
<li>Remove WordPress Meta Generator Tag 
 The WordPress Meta tag contains your WordPress version number which is best kept hidden
 </li>
<li>Remove WPML (WordPress Multilingual Plugin) Meta Generator Tag 
 This discloses the WordPress version number which is best kept hidden.
 </li>
<li>Remove Slider Revolution Meta Generator Tag 
 Slider revolution stays on the radar of hackers due to its popularity. An overnight hack in the version you’re using could lead your website vulnerable too. Make it difficult for hackers to exploit the vulnerabilities by disabling version number disclosure here
 </li>
<li>Remove WPBakery Page Builder Meta Generator Tag 
 Common page builders often are diagnosed with a vulnerability putting your website’s security at risk. With this toggle enabled, the version of these page builders will be hidden making it difficult for hackers to find if you’re using a vulnerable version.
 </li>
<li>Remove Version from Stylesheet 
 Many CSS files have the WordPress version number appended to their source, for cache purposes. Knowing the version number allows hackers to exploit known vulnerabilities.
 </li>
<li>Remove Version from Script 
 Many JS files have the WordPress version number appended to their source, for cache purposes. Knowing the version number allows hackers to exploit known vulnerabilities.
 </li>
</ol>
Basic Server Hardening
<ol>
<li>Hide Directory Listing of WP includes 
WP-includes directory gives away a lot of information about your WordPress to hackers. Disable it by simply toggling the option to ensure you make reconnaissance of hackers difficult</li>
</ol>

Security Headers
<ol>
<li>Clickjacking Protection 
Protect your WordPress Website from clickjacking with the X-Frame-Options response header. Clickjacking is an attack that tricks a user into clicking a webpage element which is invisible or disguised as another element.</li>
<li>XSS Protection 
Add the HTTP X-XSS-Protection response header so that browsers such as Chrome, Safari, Microsoft Edge stops pages from loading when they detect reflected cross-site scripting (XSS) attacks.</li>
<li>Content Sniffing protection 
Add the X-Content-Type-Options response header to protect against MIME sniffing vulnerabilities. Such vulnerabilities can occur when a website allows users to upload content to a website, however the user disguises a particular file type as something else. This can give them the opportunity to perform cross-site scripting and compromise the website.
</li>
<li>HTTP only & Secure flag 
Enable the HttpOnly and secure flags to make the cookies more secure. This instructs the browser to trust the cookie only by the server, which adds a layer of protection against XSS attacks.</li>
</ol>

WP Hardening (discontinued)

The WP Hardening is a one-click tool to fix standard security recommendations on your WordPress website.

REST XML-RPC Data Checker vs WP Hardening (discontinued)