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.

Vikash Chand

<h4>What Is xmlrpc.php?</h4>
<p><a href="http://www.xmlrpc.com/" rel="nofollow ugc">XML-RPC</a> is a remote procedure call (RPC) protocol, a feature included in WordPress, which enables data to be transmitted. It uses HTTP as the transport mechanism, and XML to encode its calls.</p>
<p>Unless you use remote technologies and mobile applications to update your WordPress site, you might not be familiar with XML-RPC. For the uninitiated, you can use xmlrpc.php to establish a remote connection to WordPress, and make updates to your site without directly logging in to your WordPress system.</p>
<p>XML-RPC is indeed useful for enabling remote connections between various external applications and WordPress. On the other hand, disabling this feature can help improve your site’s security.</p>
<h4>Why You Should Disable xmlrpc.php?</h4>
<p>The problem is that xmlrpc.php poses a security risk. It creates an additional access point to your site, which could leave it vulnerable to external attacks. Every time you authenticate XML-RPC, you need to supply your username and password. As you can imagine, this isn’t exactly ideal for security purposes.</p>
<p>For example, in order to prevent brute force attacks, you can limit login attempts on your WordPress site. However, with XML-RPC enabled, that limit does not exist. There’s no capping on login attempts, which means it’s only a matter of time before a determined cybercriminal gains access.</p>
<p>By disabling the feature, you are closing a potential area of entry for hackers.</p>
<p>XML-RPC functionality is turned on by default since WordPress 3.5. This plugin completely disables the XML-RPC API which can be abused by hackers on a WordPress site, providing an easy and simple way to disable/enable the XML-RPC API.</p>
<h4>Requirements</h4>
<ul>
<li>WordPress 3.8.1 or higher.</li>
</ul>


Simple XML-RPC Disabler

This plugin completely disables the XML-RPC API which can be abused by hackers on a WordPress site, providing an easy and simple way to disable/enable …

Extended API over XMLRPC vs Simple XML-RPC Disabler