Accepting projects ·CZ Get in touch →

XML-RPC and the user list: the forgotten doors of WordPress

Four in ten company websites on WordPress have xmlrpc.php open. What these doors allow and how to close them, even on Windows hosting.

Besides the login page, WordPress has other entrances the website owner usually doesn't know about. Two of them make password guessing easier for attackers: the XML-RPC interface and the public list of users. We show how to find them and close them.

What these doors are

XML-RPC (the file xmlrpc.php) is an old interface for controlling a website remotely. It was used mainly by mobile apps and so-called pingbacks. Most websites don't need it today, but WordPress leaves it on. It lets an attacker send many login attempts in a single request, and so get around some of the protections that watch the login page.

The user list is at /wp-json/wp/v2/users. The REST interface returns the names of the accounts that publish on the website. The attacker doesn't have to guess whether the administrator is called admin. They have the username and only guess the password.

Neither of these opens the website on its own. Together, though, they give the attacker a name and a convenient way to try passwords.

How common it is

From mid-April to the end of May 2026, the Vulscan security scanner went through the public websites of 8,307 Czech companies. 3,038 of them ran on WordPress. Of those:

FindingWebsitesShare of WordPress sites
open xmlrpc.php1,21840.1%
public user list1,67555.1%
both at once79626%

So roughly one in four company WordPress websites has both doors open at the same time. For comparison, in the same survey roughly every second website had an exploitable finding of high or critical severity. On WordPress websites it was 69%, on the others 15%. An open interface and public usernames add to that, because they can be found automatically.

How to check your own website

  1. Open https://yourwebsite.com/xmlrpc.php in your browser. If you see the sentence “XML-RPC server accepts POST requests only.”, the interface is on and reachable.
  2. Open https://yourwebsite.com/wp-json/wp/v2/users. If you see text with names and a slug field, the user list is public.
  3. Also try https://yourwebsite.com/?author=1. If the website redirects you to an address with the author's name, it gives names away this way too.

How to close them

First check whether anything uses XML-RPC. Typically older WordPress mobile apps or some plugins that connect to other services. If nothing does, block the file directly on the server. On hosting with Apache, it's enough to add this to .htaccess:

<Files xmlrpc.php>
    Require all denied
</Files>

Restrict the user list so only logged-in users can see it. A small plugin or a few lines in the theme will do it. And whether it's blocked or not, give administrators strong passwords and two-factor login.

On a company website on shared Windows hosting, the scan showed both an open xmlrpc.php and a public user list. The server there runs on IIS, where the .htaccess file does nothing, so we wrote both rules as web.config.

Lukáš Hrubý Managing director, HRUBY Software

When the website runs on Windows

Guides on the internet assume an Apache server and a .htaccess file. Some Czech shared hosting providers, however, run WordPress on Windows with an IIS server. There the rules go into the web.config file in the website root:

<security>
  <requestFiltering>
    <denyUrlSequences>
      <add sequence="/xmlrpc.php" />
      <add sequence="/wp-json/wp/v2/users" />
    </denyUrlSequences>
  </requestFiltering>
</security>

The block belongs in the system.webServer section. If web.config already exists, add the rules to it, don't overwrite it. And download a backup before editing it: a mistake in this file takes the whole website down.

When to call in an expert

Anyone with FTP access can block two files. Help pays off when you don't know whether something important uses the interface, when the website runs on unusual hosting, or when you want to know what other doors the website has. A security audit also covers outdated plugins, forgotten files and domain settings.

Written by Ing. Lukáš Hrubý, HRUBY Software · ← All articles

Dealing with the same thing?

We'll look at it with you. The first consultation is free. More about the service: Security Audits.

Book a consultation →
// Contact

Get in touch.

Tell us what you need, or just call. We reply within one business day.

// Encrypted in transit · privacy policy