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.

Lars Koudal

cleverplugins

<p>Prevent your WordPress site from participating and being a victim of pingback denial of service attacks. <strong>After activation the plugin automatically disables XML-RPC. There’s no need to configure anything.</strong></p>
<p>By disabling the XML-RPC pingback you’ll:<br />
* lower your server CPU usage<br />
* prevent malicious scripts from using your site to run pingback denial of service attacks<br />
* prevent malicious scripts to run denial of service attacks on your site via pingback</p>
<p>From sucuri.net:</p>
<blockquote>
<p>Any WordPress site with Pingback enabled (which is on by default) can be used in DDOS attacks against other sites.</p>
</blockquote>
<h4>Learn More</h4>
<ul>
<li><a href="http://wptavern.com/how-to-prevent-wordpress-from-participating-in-pingback-denial-of-service-attacks" rel="nofollow ugc">How To Prevent WordPress From Participating In Pingback Denial of Service Attacks</a> – wptavern.com</li>
<li><a href="http://blog.sucuri.net/2014/03/more-than-162000-wordpress-sites-used-for-distributed-denial-of-service-attack.html" rel="nofollow ugc">More Than 162,000 WordPress Sites Used for Distributed Denial of Service Attack</a> – sucuri.net</li>
<li><a href="http://hackguard.com/xmlrpc-php-ping-backs-hackers-denial-service-attacks" rel="nofollow ugc">xmlrpc.php and Pingbacks and Denial of Service Attacks, Oh My!</a> – hackguard.com</li>
</ul>
<h4>Is Your Site Attacking Others?</h4>
<p>Use <a href="http://labs.sucuri.net/?is-my-wordpress-ddosing" rel="nofollow ugc">Sucuri’s WordPress DDOS Scanner</a> to check if your site is DDOS’ing other websites</p>
<h4>Why Not Just Disable XMLRPC Altogether?</h4>
<p>Yes, you can choose to do that, but if you use popular plugins like JetPack (that use XMLRPC) then those plugins will stop working. That is why this small plugin exists.</p>


Remove & Disable XML-RPC Pingback

Great plugin, super easy to install and just sits there doing it's job. Very light as well, so has no effects that I could see, on site speed or memory usage. Can't think of a reason why you wouldn't be using this to be honest. Thanks for developing it!

Just what I needed

Prevent pingback, XML-RPC and denial of service DDOS attacks by disabling the XML-RPC pingback functionality.

Extended API over XMLRPC vs Remove & Disable XML-RPC Pingback