Skip to content
TatiCreative
All articles

· 7 min read · Mert Tati

How to Disable XML-RPC in WordPress: Safely Blocking xmlrpc.php

How to disable XML-RPC in WordPress: what xmlrpc.php is, who uses it, the system.multicall risk, and the pros and cons of each way to turn it off.

Short answer: The safest way to disable XML-RPC is to turn off the xmlrpc.php methods that accept passwords, block system.multicall, and leave pingbacks on if you need them. If you don’t use Jetpack or an older app that connects through xmlrpc.php, you can shut the file off completely. You can do this with an .htaccess rule, a code filter or a plugin; whichever you choose, confirm it’s actually off with a real request.

Forgotten metal door in a back alley at night, an overlooked entrance

What is xmlrpc.php?

XML-RPC is the remote access protocol WordPress used long before the REST API existed. The xmlrpc.php file in your site’s root directory lets an external app log in with a username and password to publish posts, manage comments or upload media. Today the REST API handles most of these tasks, but xmlrpc.php still ships enabled by default for backward compatibility.

Who uses XML-RPC?

  • Jetpack: needs XML-RPC to connect to WordPress.com. If you use Jetpack, disabling it completely will break the connection.
  • The official WordPress mobile app and older desktop blogging editors: some versions and setups connect to your site through xmlrpc.php.
  • Pingbacks and trackbacks: notifications you receive when another blog links to your post. Harmless, but unimportant for most sites.
  • Some legacy integrations and remote publishing tools.

If you don’t use any of these, xmlrpc.php is nothing but attack surface for you.

Why is it a risk? system.multicall and the hidden back door

xmlrpc.php is a second login door, independent of wp-login.php. Even if you’ve moved your login page to a secret URL, bots can send requests straight to xmlrpc.php and try usernames and passwords. Worse still is the system.multicall method: a single HTTP request can bundle hundreds of calls, and therefore hundreds of password attempts. Login attempt limits often count that request as just one attempt.

We saw this firsthand with one of our clients and wrote about it in our guide to changing the WordPress login URL: even with the login URL hidden, password attempts kept coming, and the source was XML-RPC. The lesson: hiding the login page is only half a measure until XML-RPC is closed. For the bigger picture on password attacks, see our post on stopping brute-force attacks.

Pingbacks bring a separate problem: open pingbacks can let your site be used to send requests to other sites. If you don’t need pingbacks, turning them off shrinks your attack surface even further.

Ways to disable XML-RPC: pros and cons

Hand bolting a heavy metal door shut
  • 1. .htaccess or server rule: you reject requests to xmlrpc.php at the web server level. The upside is that it’s the lightest option, since PHP never runs. The downside is that it’s all or nothing: pingbacks and Jetpack go dark too; Nginx needs different syntax; the rule can be lost when you migrate servers, and it’s invisible from the WordPress dashboard.
  • 2. Code filter (xmlrpc_enabled): a filter added to your theme’s functions.php or a code snippet disables the XML-RPC methods that require authentication. The upside is that pingbacks keep working. The downside is that it doesn’t disable system.multicall on its own, and the filter disappears when you switch themes.
  • 3. Removing methods with the xmlrpc_methods filter: often recommended, but system methods such as system.multicall are added to the list by WordPress later on, so this filter can’t reliably remove them. Don’t rely on this method alone.
  • 4. Plugin: configured from a settings screen, survives theme or server changes, and usually keeps a log too. The downside is that you need to know what the plugin actually does and verify it.

If you use a CDN like Cloudflare, you can also block xmlrpc.php there with a security rule, so the request never reaches your server. This is an extra layer alongside the WordPress-side fix, not a replacement for it.

Which option is right for you?

  • WooCommerce store or corporate site without Jetpack: disable XML-RPC logins and leave pingbacks on if you like. Password guessing becomes impossible and nothing breaks.
  • Sites that don’t use Jetpack or the mobile app and don’t need pingbacks: disable it completely. This is the safest choice.
  • You have an integration that depends on XML-RPC: at the very least, disable system.multicall and make sure your login limit also counts XML-RPC attempts.
  • Not sure? Disable logins first, watch for a few days to see if anything breaks, then move to disabling it completely.

How do you verify XML-RPC is actually disabled?

A settings screen saying “disabled” doesn’t mean your site is really closed to the outside world. A cache, another plugin or a server rule in between can change the result. The only reliable way to verify is to send a real request:

  • Open yourdomain.com/xmlrpc.php in a browser. The message “XML-RPC server accepts POST requests only.” means the file is responding; on its own that doesn’t mean logins are open, but it tells you the file is reachable.
  • The real test is a POST request: call the wp.getUsersBlogs method with a wrong password. If you get an “incorrect username or password” response, logins are open; if the method is rejected or you get a 403, they’re closed.
  • Test system.multicall separately: even with logins closed, you need to check whether multicall has been disabled on its own.
  • Check your server access logs to see which response codes requests to xmlrpc.php are getting.

Doing it all with one plugin: Hushfort Surface Hardening

The Surface Hardening module in the Hushfort WordPress security plugin offers four options for XML-RPC:

  • Disable logins, keep pingbacks (recommended and default): all XML-RPC methods that require authentication are disabled, system.multicall is caught in the request body and rejected, and pingbacks and trackbacks keep working.
  • Disable completely: every request to xmlrpc.php is cut off at the very start with a 403, without loading WordPress; the RSD link in the page head and the X-Pingback header are removed as well. Jetpack and the official mobile app won’t be able to connect to the site.
  • Disable system.multicall only: for sites with an integration that depends on XML-RPC, this stops bulk password guessing.
  • Leave alone: the WordPress default.

Blocked probes can optionally be written to the History tab (once per IP every 15 minutes, so the table doesn’t balloon during an attack). The Source column in History shows whether an attempt came from the login page, XML-RPC or REST, so the question “Has the attack stopped, or can I just not see it?” never goes unanswered. The Surface Scan panel looks at what your site actually exposes, not at what the setting says: it sends a real XML-RPC login attempt to your own site, measures whether logins and multicall are open, and if they are, flags it with a red card and a “What should I do?” guide. Failed attempts over XML-RPC also count toward the lockout counter in the Limit Login module.

Once XML-RPC is closed, the next step is protecting accounts with a second layer; see our WordPress two-factor authentication (2FA) guide. If you’d rather hand your store’s security settings, along with post-launch maintenance, to a team, our Izmir-based team’s e-commerce service covers it.

Frequently asked questions

Does disabling XML-RPC affect SEO? No. Search engines don’t crawl your site via XML-RPC; your sitemap and pages are unaffected.

Will disabling XML-RPC break WooCommerce? No. WooCommerce, payment gateways and the admin dashboard run on the REST API and admin-ajax.php and don’t need XML-RPC.

Can I just delete xmlrpc.php? Not recommended. The file comes back with the next core update and your protection silently disappears. Blocking access with a rule or setting is more durable.

Why do I still see xmlrpc.php requests with XML-RPC disabled? Bots don’t know the file is closed and keep trying. What matters is that the requests are rejected; rejected requests put very little load on your server.

Summary: xmlrpc.php is a second door that bypasses a hidden login URL, and system.multicall lets attackers try hundreds of passwords in a single request. If you don’t use Jetpack, disable logins or shut the file off completely, always block multicall, and verify the result with a real request, not a settings screen.

More articles

Request a call

Describe your project in 60 seconds.

Fill in the short pre-form; we'll match you with the right person and reply within 24 hours.

A native English-speaking Project Lead from our team runs your project with you.

01 / 04

Which areas do you need help with?

  • UI/UX & Product Development
  • AI Solutions
  • Graphic & Brand Design
  • Software & Hosting
  • Studio & Production
  • Social Media
  • Digital Marketing
  • Digital Transformation
  • Industrial IoT (IIoT)
Average response time< 24 hours