You are here: Sysadmins of the North » Web applications » Web application security » Protect WordPress from brute-force XML-RPC attacks

Protect WordPress from brute-force XML-RPC attacks

The WordPress XML-RPC API has been under attack for many years. Back in August 2014, WordPress released version 3.9.2, fixing a possible denial of service issue in PHP’s XML processing. There are brute-force amplification attacks, reported by Sucuri, and so on. So, how do you protect WordPress from these xmlrpc.php attacks, optionally still being able to use (some of) its functionality like Jetpack? This post gives you some insights.

The problem: during a brute-force attack, HTTP requests keep coming in, knocking down webservers due to the sheer number of HTTP POST requests for /xmlrpc.php, and the increasing number of running PHP processes. This often consumes all available CPU and memory: a typical xmlrpc.php attack characteristic.

You want to protect your website and somehow block requests to xmlrpc.php. But you also want to use (some of) its functionality, like WordPress Jetpack. How?

One option is to add IP addresses to an allow list for xmlrpc.php access through web.config in Windows Server IIS or .htaccess in Linux Apache, and block everything else.

WordPress xmlrpc.php allow list for, Automattic & Jetpack IP addresses

In a WordPress support ticket Jeremy Herve (@jeherve) provides some information about the required IP addresses in use for WordPress, Jetpack and other services.

If your hosting provider doesn’t want to allow all connections to Jetpack, you can use these IPs:

All of the IPs listed at

So you need to allow these IP addresses. One big advantage of using an allow list, is that you automatically block all other IP’s. Extra security for free :)

Add your own IP to the list if you need access too.

Create an IP allow list for xmlrpc.php in Windows Server IIS web.config

You can use the following web.config snippet to allow IP addresses and ranges (netblocks) access to the xmlrpc.php file. All other IP addresses are blocked. The location tag means the rules only apply to the path mentioned. In this case the file xmlrpc.php.

<location path="xmlrpc.php">
      <ipSecurity allowUnlisted="false">
        <add ipAddress="" subnetMask="" allowed="true" />
        <add ipAddress="" subnetMask="" allowed="true" />
        <add ipAddress="" subnetMask="" allowed="true" />
        <add ipAddress="" subnetMask="" allowed="true" />
        <add ipAddress="" subnetMask="" allowed="true" />
        <add ipAddress="" subnetMask="" allowed="true" />
        <add ipAddress="2a04:fa80::" subnetMask="ffff:fff8::" allowed="true" />
        <add ipAddress="2620:115:C000::" subnetMask="ffff:ffff:ff00::" allowed="true" />
</location>Code language: HTML, XML (xml)

Apache .htaccess mod_authz_host IP allow list equivalent

If you are on a Linux platform with Apache as its webserver, you can use the following .htaccess equivalent to create an allow list.

When using Apache 2.4.6+, you need to use a slightly different syntax for the Apache module mod_authz_host:

<Files xmlrpc.php>
  # Help:
  Require all denied
  Require ip
  Require ip
  Require ip
  Require ip
  Require ip
  Require ip
  Require ip 2620:115:C000::/40
  Require ip 2a04:fa80::/29
</Files>Code language: Apache (apache)

Learn the WordPress .htaccess security best practices in Apache.

The example below is only for Apache 2.2, it’s old and deprecated, but is mentioned here for completeness.

# Block access to xmlrpc.php for everyone 
# except and Jetpack IP addresses.
# AllowList IP ranges in Apache 2.2 .htaccess using mod_authz_host:
<Files xmlrpc.php>
  order deny,allow
  allow from
  allow from
  allow from
  allow from
  allow from
  allow from
  allow from 2620:115:C000::/40
  allow from 2a04:fa80::/29
  deny from all
</Files>Code language: Apache (apache)

What if WordPress/Jetpack IP addresses change?

Unfortunately you need to regularly check to see if IP blocks have changed. Other options do exist. I hope this’ll help you in keeping your site safe!

Block access to the xmlrpc.php file completely

Are you looking for rock solid, eco-friendly, WordPress hosting? Look no further! UmbHost got you covered, offering hosting services for websites and businesses of all sizes.

Another solution is to block requests to /xmlrpc.php completely, meaning you cannot use a plugin like Jetpack, or other functionality that relies on XML-RPC.

By Files directive in .htaccess

<Files xmlrpc.php>
       Require all denied
</Files>Code language: Apache (apache)

By IIS requestFiltering in web.config

In your IIS web.config file, add in the appropriate place:

      <add sequence="xmlrpc.php" />
</security>Code language: HTML, XML (xml)

Using a Rewrite Rule


RewriteEngine on
RewriteRule \Qxmlrpc.php\E - [F,L,NC]Code language: Apache (apache)


<rule name="Block contact form spam" stopProcessing="true">
  <match url="(.*)" ignoreCase="true" />
    <conditions logicalGrouping="MatchAll">
      <add input="{URL}" pattern="/xmlrpc.php" ignoreCase="true" negate="false" />
      <add input="{REQUEST_METHOD}" pattern="POST" ignoreCase="true" negate="false" />
  <action type="CustomResponse" statusCode="403" statusReason="Forbidden" statusDescription="Forbidden" />
</rule>Code language: HTML, XML (xml)

Update: renamed “whitelist” to “allow list”.

Conclusion and giveaway

This isn’t the first post on Sysadmins of the North about XML-RPC, blocking access to a file, securing WordPress or .htaccess/web.config files. Check out these gems:

3 thoughts on “Protect WordPress from brute-force XML-RPC attacks”

  1. I want to remove xmlrpc.php from source code on all pages on WordPress website. please provide a solution.

  2. You can take a look to REST XML-RPC Data Checker ( plugin: it allows an extended access control to the XML-RPC and REST APIs (enabling also by user/IP/method or endopoint)

    REST Api is enabled by default and you should to know that this way, a WordPress instance is potentially leaking data (for example anyone could be able to copy easily your published contents natively, get the list of all users or retrieve other information that you didn’t want to be public).

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top