Phil Erb

Solve the Net

<p>Pretty simply, this plugin uses the built-in WordPress filter “xmlrpc_enabled” to disable the XML-RPC API on a WordPress site running 3.5 or above.</p>
<p>Beginning in 3.5, XML-RPC is enabled by default. Additionally, the option to disable/enable XML-RPC was removed. For various reasons, site owners may wish to disable this functionality. This plugin provides an easy way to do so.</p>


Disable XML-RPC


Dead simple as it should be. Nice, thank you for that.


Reduced to perfection

Disables the XML-RPC API in WordPress 3.5+, which is enabled by default.

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.

Disable XML-RPC vs Manage XML-RPC