realflash

<p>A WordPress plugin that allows access to the whole WP API via XML-RPC.</p>
<h3>What does it do?</h3>
<p>The full WP API is comprehensive, but most of it is only available to plugin code, not remotely. The official WP XML-RPC API is much smaller. This plugin opens up access to that full internal API remotely so that you can do whatever you want over XML-RPC.</p>
<h3>Which methods does it allow me to call?</h3>
<p>Anything in the <a href="https://codex.wordpress.org/Function_Reference" rel="nofollow ugc">WordPress Function Reference</a> that your username has access to.</p>
<h3>How do I use it?</h3>
<p>First you should make sure that you have working code that can interact with the standard supported methods in the <a href="https://codex.wordpress.org/XML-RPC_WordPress_API" rel="nofollow ugc">XML-RPC WordPress API</a>. Once you do, you are ready to use this plugin. See also <a href="https://codex.wordpress.org/XML-RPC_Support" rel="nofollow ugc">About WordPress XML-RPC Support</a>.</p>
<p>Simply set the method name to wpext.callWpMethod, and then pass the WP API method name that you want to call as the first parameter, followed by any other parameters meeded by that method. Exactly how you do this depends upon the XML-RPC client library you are using in your code. So (for example), if you are currently using the XML-RPC API like this:</p>
<pre><code>$xmlrpc_client->call('wp.getComment', 5);
</code></pre>
<p>then instead do this:</p>
<pre><code>$xmlrpc_client->call('wpext.callWpMethod', 'wp_create_user', $new_username, $new_password, $new_email);
</code></pre>
<p>or</p>
<pre><code>$xmlrpc_client->call('wpext.callWpMethod', 'wp_delete_user', $id_to_delete);
</code></pre>
<p>These examples are pseudo-code: they do not relate to a specific XML-RPC client.</p>
<h3>Settings</h3>
<p>There is only one, and that is the list of functions that should be allowed over XML-RPC. See Settings > Extended API in your dashboard to set it. To allow one additional function, simply set it to the name of that function:</p>
<pre><code>wp_create_user
</code></pre>
<p>To specify multiple functions, separate with commas:</p>
<pre><code>wp_create_user,wp_delete_user[,method3]...
</code></pre>
<p>To protect you from yourself, this setting comes with a dummy value that does not correspond to a real method. This is to force you to think about what methods you really need to enable. If you set this value to the empty string (blank), all methods are allowed.</p>
<h3>Security</h3>
<p>There are good reasons why the XML-RPC API only has limited methods. Think carefully about whether this plugin is right for your situation, and only enable the methods you really need.</p>


Extended API over XMLRPC

A WordPress plugin that allows access to the whole WP API via XML-RPC.

Amin Nazemi

Neatma

<p>Protect your website from xmlrpc brute-force attacks,DOS and DDOS attacks, this plugin disables the XML-RPC and trackbacks-pingbacks on your WordPress website.</p>
<p><strong>PLUGIN FEATURES</strong><br />
(These are options you can enable or disable each one)</p>
<ul>
<li>Disable access to xmlrpc.php file using .httacess file </li>
<li>Automatically change htaccess file permission to read-only (0444)</li>
<li>Disable X-pingback to minimize CPU usage </li>
<li>Disable selected methods from XML-RPC</li>
<li>Remove pingback-ping link from header</li>
<li>Disable trackbacks and pingbacks to avoid spammers and hackers</li>
<li>Rename XML-RPC slug to whatever you want</li>
<li>Black list IPs for XML-RPC</li>
<li>White list IPs for XML-RPC</li>
<li>Some options to speed-up your wordpress website</li>
<li>Disable JSON REST API</li>
<li>Hide WordPress Version</li>
<li>Disable built-in WordPress file editor</li>
<li>Disable wlw manifest</li>
<li>And some other options</li>
</ul>
<p><strong>What is XMLRPC</strong></p>
<p>XML-RPC, or XML Remote Procedure Call is a protocol which uses XML to encode its calls and HTTP as a transport mechanism.<br />
Beginning in WordPress 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>
<p><strong>Why you should disable XML-RPC</strong><br />
<em>Xmlrpc has two main weaknesses</em></p>
<ul>
<li>Brute force attacks:<br />
Attackers try to login to WordPress using xmlrpc.php with as many username/password combinations as they can enter. A method within xmlrpc.php allows the attacker to use a single command (system.multicall) to guess hundreds of passwords. Daniel Cid at Sucuri described it well in October 2015: “With only 3 or 4 HTTP requests, the attackers could try thousands of passwords, bypassing security tools that are designed to look and block brute force attempts.”</li>
<li>Denial of Service Attacks via Pingback:<br />
Back in 2013, attackers sent Pingback requests through xmlrpc.php of approximately 2500 WordPress sites to “herd (these sites) into a voluntary botnet,” according to Gur Schatz at Incapsula. “This gives any attacker a virtually limitless set of IP addresses to Distribute a Denial of Service attack across a network of over 100 million WordPress sites, without having to compromise them.”</li>
</ul>


Disable XML-RPC-API

The upgrade notice keeps coming back on every screen even after being dismissed. It looks very unprofessional to my clients and is embarrassing for me as a web developer, i would rather disable the plugin and use the code in a function. 

It should be permanently dismissible via a cookie, like for other plugins. It might be ok once, when the plugin is first installed or updated, but after that, it should never appear again. 

Good plugin, but upgrade nag is too annoying

A simple and lightweight plugin to disable XML-RPC API, X-Pingback and pingback-ping in WordPress 3.5+ for a faster and more secure website

Extended API over XMLRPC vs Disable XML-RPC-API