WordPress login attacks and XML-RPC

Version 1.1 — 2026-11-01

If your site's login page is being hit by bots, this page explains what is happening, what we changed on your server, and what you need to do — which is usually nothing.

What is happening

Automated scanners constantly probe WordPress sites for three things: wp-login.php, xmlrpc.php, and old plugins with known holes. These are not attacks aimed at you. They are bulk sweeps — the same script hitting tens of thousands of sites, looking for the one that answers.

xmlrpc.php is the file they like best, because one request can carry hundreds of password attempts at once. That is why a quiet site can suddenly show thousands of log lines in a night, and why the site may feel slow while it happens: every attempt wakes WordPress up to say no.

Why we do not simply delete xmlrpc.php

Because Jetpack needs it, and so do the WordPress and WooCommerce mobile apps. They reach your site over XML-RPC: block the file outright and those integrations stop — stats stop, backups stop, publishing from the app stops.

So we do not choose between "open to everyone" and "delete the file". We close it by default, and open it per site for the integrations you actually use.

What AdocSys does instead

xmlrpc.php refuses everyone by default. We then open it, site by site, for the integrations you ask us to allow.

  • Requests are refused with a 403 before WordPress is even loaded — so a bot costs us a log line, not a PHP process.
  • That refusal is the default on every WordPress site we host.
  • If you use Jetpack, the WordPress app or the WooCommerce app, we add that vendor's published address ranges to your site's allowlist. Jetpack traffic is accepted; everyone else still gets a 403.
  • Repeated abusive requests are banned at the firewall (fail2ban) for an hour, which stops the noise at the source.
  • wp-login.php is rate-limited in the same way. The login form still works normally for you. A script gets 4 tries, then a 20-minute lockout — and after four of those, 24 hours. Ten failures in ten minutes also earn an hour at the firewall.

What changes for you

Nothing, unless you publish from an app. You log in as usual, and the site is faster under these sweeps because the requests never reach WordPress.

If you use Jetpack or a mobile app, ask us once and we enable it for that site. Until then, that integration will not connect — that is a deliberate trade: no unauthenticated remote access unless you need it.

You will not receive an alert for this. A blocked bot is a success, not an incident — we would only contact you if something actually got in.

What we ask of you

  • Tell us when you add a service that needs XML-RPC — Jetpack, the WordPress or WooCommerce app, a publishing tool, an old integration. We enable it for that site in minutes, which beats debugging a mystery outage later.
  • Two-step login, or a passkey, on every administrator account.
  • A long, unique password for the admin account — a password manager, not memory.
  • Never a user named admin. It is the first guess every script makes.
  • Keep WordPress, themes and plugins updated — most real break-ins come from an outdated plugin, not from the login page.

The honest limits

  • This does not make a weak password safe. It removes the loudest door, not the need for a real lock.
  • The allowlist is maintained by us. Jetpack publishes its ranges and we review them; if Jetpack ever changes them, we update the rule — the same way we track every other vendor notice.
  • A closed endpoint is the default, not a fault. If an integration that used to work stops working, the missing allowlist entry is the first thing to check — and the reason to tell us before you need it.
  • wp-login.php cannot be closed the same way, because you need it. That is why the rate limit, the firewall ban and two-step login are not optional extras.

How to verify it

Ask us, or run it yourself from outside the network:

curl -sI https://your-domain.tld/xmlrpc.php

A 403 is the correct answer. A 405 means the file is still answering to everyone — tell us, because the rule is not in place on that site. On Windows 10 or 11, run it as curl.exe — PowerShell uses that name for something else. No terminal handy? Open https://your-domain.tld/xmlrpc.php in a browser: “XML-RPC server accepts POST requests only” means the file is answering to everyone.

Then check from Jetpack's side: paste your address into jetpack.com/support/debug, which tests from outside your site, and look for the Jetpack Connection checks under Tools → Site Health. Both should read healthy, with no “XML-RPC blocked” notice. If that test fails and you use Jetpack, ask us for the allowlist entry — it is the expected result on a site we have not enabled it for.


Questions: support@adocsys.net · 1 877 749-9579

Was this answer helpful? 0 Users Found This Useful (0 Votes)