Explainers · Explainer
What Is XML-RPC? A Plain Explanation

Short answer
XML-RPC is an old remote access protocol that lets outside apps talk to your WordPress site by sending commands over HTTP. It has been enabled by default since WordPress 3.5, and it is a known target for brute-force logins and pingback attacks. Most sites no longer need it, because the REST API handles the same jobs, so disabling it is a common hardening step.
Key takeaways
- XML-RPC is a protocol that encodes remote commands in XML and sends them over HTTP.
- It has been enabled by default since WordPress 3.5, and the admin area has no switch to turn it off.
- The system.multicall method lets attackers test hundreds of passwords in a single request.
- In 2013, attackers used pingbacks on about 2,500 WordPress sites to build a botnet.
- Disabling XML-RPC breaks the mobile apps, some Jetpack features, and pingbacks, but not the editor.
- Visiting xmlrpc.php should return a 403 error once the block is working.
What is XML-RPC in WordPress?
XML-RPC is an old remote access protocol that lets outside apps talk to your WordPress site by sending commands over HTTP.
XML-RPC stands for XML Remote Procedure Call. WordPress.org describes it as a protocol that uses XML to encode its calls and HTTP as a transport mechanism. In plain terms, an app sends your site an XML message that says “do this”, and your site sends back an XML message with the result.
It was built for a time when desktop blogging apps and remote editors were the main way to publish from outside the admin area. Today, most of that work has moved to the WordPress REST API, which sends data as JSON instead of XML. WordPress REST API Handbook
XML-RPC is still part of WordPress core, and it is turned on by default. Beginning in WordPress 3.5, XML-RPC has been enabled by default, and the option to turn it off was removed, according to the WordPress.org plugin page.
How does XML-RPC work?
An outside app sends an XML request to your site, WordPress runs the command in that request, and sends back an XML reply.
Each request names a method, such as publishing a post or fetching a list of posts, and carries the login details needed to run it.
WordPress checks the login, runs the method, and returns the result in the same XML format. The app never loads the admin screens; it talks to the site through this one channel.
The key detail is that the login travels inside the request itself. That is what makes XML-RPC handy for apps, and it is also what makes it a target, because anyone on the internet can send requests to the same endpoint and try logins.
A request can also bundle many method calls into one message using system.multicall. That feature was meant to save time, but it lets an attacker pack hundreds of password guesses into a single HTTP request, as explained in the section on security risks below.
PHP itself has two settings for XML-RPC errors, xmlrpc_errors and xmlrpc_error_number, listed in the PHP manual.
What is xmlrpc.php?
xmlrpc.php is the single file in your WordPress root folder that receives every XML-RPC request.
Every XML-RPC call goes to https://example.com/xmlrpc.php, using your own domain in place of example.com. The file is part of WordPress core, so it exists on every WordPress site, even if nothing on the site uses it.
Visiting xmlrpc.php in a browser shows a short message that says “XML-RPC server accepts POST requests only.” That message tells you the endpoint is live and waiting for requests. It does not mean your site is broken; it means the file is there and answering.
Because the file sits in the root folder next to wp-admin and wp-content, it is easy to find and easy to block. The blocking methods in this guide all work by stopping requests to this one file.
What still uses XML-RPC today?
The WordPress mobile apps, some Jetpack features, remote publishing tools, and pingbacks still use XML-RPC.
| Service | Needs XML-RPC? | Note |
|---|---|---|
| WordPress mobile apps | Yes | The apps connect through XML-RPC |
| Jetpack | Some features | Only the features that rely on XML-RPC |
| Remote publishing clients | Yes | Desktop editors that post from outside WordPress |
| Pingbacks and trackbacks | Yes | They arrive through xmlrpc.php |
| Block editor and modern apps | No | They use the REST API instead |
The WordPress.org plugin pages list the same set: turning XML-RPC off may affect the WordPress mobile apps, Jetpack features that require XML-RPC, remote XML-RPC publishing clients, and trackbacks and pingbacks. Simple Disable XML-RPC
If you only write in the WordPress admin area and never use the mobile app, you probably do not need XML-RPC at all. Most sites fall in that group, which is why disabling it is a common hardening step.
Why is XML-RPC a security risk?
XML-RPC is a risk because it gives attackers a login endpoint that skips the normal login page and lets them test many passwords in very few requests.
The first weakness is brute-force amplification through system.multicall. One request can bundle hundreds of login attempts, so the login page limits that protect wp-login.php never see them.
The second weakness is denial-of-service attacks through pingbacks. Back in 2013, attackers sent pingback requests through xmlrpc.php on about 2,500 WordPress sites to herd them into a voluntary botnet, according to Gur Schatz at Incapsula, as quoted on the WordPress.org plugin page.
Each site then sent requests to the victim, so the attack came from thousands of addresses at once.
The third weakness is resource use. Automated scanners probe xmlrpc.php on every WordPress site they find, and each probe makes WordPress load and run code. On a small shared hosting plan, a steady stream of probes can eat CPU and memory that your visitors need.
None of this means every site with XML-RPC on will be hacked. It means the endpoint is a known, heavily scanned target, and turning it off removes that target entirely.
Should you disable XML-RPC?
Yes, disable XML-RPC if you do not use the mobile apps, Jetpack features that need it, or a remote publishing tool.
For most sites, that is the right call. The WordPress.org plugin page for Simple Disable XML-RPC says that if you do not use these services, disabling XML-RPC is strongly recommended.
Simple Disable XML-RPC The modern replacement is the REST API, which the REST API Handbook describes as the foundation of the block editor, and which uses JSON instead of XML.
Keep it on only when something you rely on needs it. The two common cases are posting from the official WordPress mobile app and a Jetpack feature that still uses XML-RPC. If you are not sure, turn it off and watch for a week; if an app stops connecting, turn it back on.
If you keep it on, add a second layer. A login-limit plugin or a firewall can cap failed attempts, and the Disable XML-RPC dashboard plugin on WordPress.org limits failed logins to 5 per hour per IP address.
How to set up the Wordfence firewall Rate limiting helps, but it does not close the endpoint the way disabling does.
How do you disable XML-RPC?
The simplest way to disable XML-RPC is a one-line filter in a small plugin or your theme code, or a plugin from WordPress.org.
Add this line to a small custom plugin or a code-snippets plugin:
add_filter( 'xmlrpc_enabled', '__return_false' );
The xmlrpc_enabled filter is the native WordPress switch for this feature, and the Simple Disable XML-RPC plugin on WordPress.org uses the same filter to turn XML-RPC off safely. Simple Disable XML-RPC Do not edit a theme file directly for this, because a theme update can wipe the change.
If you would rather not add code, install a plugin from WordPress.org, such as Simple Disable XML-RPC. Go to Plugins, then Add New, search for the plugin name, and click Install Now and Activate. The plugin turns XML-RPC off when it activates, and you can turn it back on from its settings page.
A third option is to block the file in .htaccess on an Apache server. Add a Files block for xmlrpc.php with Order Deny,Allow and Deny from all.
This stops requests before WordPress loads, which also saves server resources. Ask your host whether your server runs Apache before you use this method, because it does nothing on Nginx.
How do you check that XML-RPC is off?
Visit https://example.com/xmlrpc.php in your browser, using your own domain, and look for a 403 Forbidden error.
The WordPress.org plugin page gives this as the easiest check: open the xmlrpc.php address, and if you see “Access forbidden!” or a “403 error”, the block is working. If you still see “XML-RPC server accepts POST requests only”, the endpoint is still live.
A second check is the WordPress mobile app. Try to connect, and the app should tell you that “XML-RPC services are disabled on this site” when the block is active. Some disable plugins also include a test button on their settings page that sends a request and reports whether the endpoint returns a 403.
Check again after any big change, such as a host move or a security plugin update, because a new setup can turn the endpoint back on without telling you.
What breaks when you disable XML-RPC?
Disabling XML-RPC breaks the WordPress mobile apps, some Jetpack features, remote publishing clients, and pingbacks and trackbacks.
The mobile apps connect through XML-RPC, so they stop working until you turn it back on. If you write posts from your phone, test the app after you disable the endpoint, and re-enable it if the app cannot connect, as covered in this guide to WordPress security.
Jetpack is a mixed case. Some of its features use XML-RPC and some do not, so disabling the endpoint may break only part of Jetpack.
Jetpack connects your site to WordPress.com through XML-RPC, and blocking xmlrpc.php breaks that connection, according to Jetpack's own support page. Jetpack shows a notice in WP Admin when this happens.
Pingbacks and trackbacks also stop, because they arrive through xmlrpc.php. Most sites never notice, since pingbacks are rarely read, and you can turn them off separately under Settings, then Discussion, if you do not want them at all.
Nothing else breaks. The admin area, the block editor, themes, plugins, and the REST API all keep working, because none of them use XML-RPC.
The REST API handles the same jobs with JSON, and the REST API Handbook notes that it applies the same authentication rules as the rest of WordPress.
What mistakes should you avoid with XML-RPC?
The mistakes to avoid are assuming it is off, blocking it in only one place, and forgetting what still needs it.
- Assuming it is off. XML-RPC has been on by default since WordPress 3.5, and there is no setting in the admin area to turn it off, so check the endpoint instead of guessing.
- Blocking it in only one place. If you use both a code filter and a server rule, make sure they agree, or one can undo the other after an update.
- Forgetting the mobile app. If you post from your phone, test the app after disabling XML-RPC, or you may find out it broke when you next need it.
- Editing core files to remove xmlrpc.php. Deleting the file does nothing lasting, because the next WordPress update puts it back. Use the filter or a plugin instead.
- Ignoring the logs. A sudden rise in xmlrpc.php requests in your server logs is a sign of a brute-force attempt, and it is worth checking even when the endpoint is blocked.
Frequently asked questions
Is it safe to disable XML-RPC?
Yes, for most sites. If you do not use the WordPress mobile app, a Jetpack feature that needs XML-RPC, or a remote publishing tool, turning it off removes a known attack target and changes nothing you use. Test your apps after disabling it, and turn it back on if something stops connecting.
How do I check if XML-RPC is disabled on my site?
Open the xmlrpc.php address on your own site in your browser, using your own domain. If you see a 403 Forbidden error or the words Access forbidden, the block is working. If you see the message XML-RPC server accepts POST requests only, the endpoint is still live.
Why is XML-RPC dangerous?
The main risk is brute-force logins. The system.multicall method lets an attacker test hundreds of passwords in a single request, skipping the limits that protect the normal login page. Pingbacks can also be abused to turn many sites into a botnet that floods one victim.
Will disabling XML-RPC break my site?
No. The block editor, themes, plugins, and the admin area do not use XML-RPC. The WordPress mobile apps, some Jetpack features, remote publishing clients, and pingbacks stop working, but the REST API takes over the same jobs for modern apps and editors.
Can I disable XML-RPC without a plugin?
Yes. Add the line add_filter( 'xmlrpc_enabled', '__return_false' ); to a small custom plugin or a code-snippets plugin. A plugin from WordPress.org, such as Simple Disable XML-RPC, does the same thing without code. Do not edit a theme file directly, because an update can wipe the change.
Sources
- Disable XML-RPC-API plugin WordPress.org
- Simple Disable XML-RPC plugin WordPress.org
- Disable XML-RPC - Dashboard Control plugin WordPress.org
- REST API Handbook Developer.WordPress.org
- Jetpack and XML-RPC Jetpack
- Errors and Logging Configuration Options PHP.net
Is your product missing, or something out of date?
Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.
Thanks — we review requests within 3 business days.
Related guides
About the editors
Researched from the primary sources listed above and checked against our editorial rules before publishing.


