Skip to content

Server load spikes from thousands of POSTs to xmlrpc.php

XML-RPC is barely used anymore but constantly abused for brute-force amplification.

Try this first

  1. 1Check access logs for spikes on /xmlrpc.php
  2. 2Add a block in .htaccess or nginx config that denies xmlrpc.php
  3. 3Or in functions.php: add_filter('xmlrpc_enabled', '__return_false')
  4. 4Verify Jetpack or mobile apps still work, otherwise selectively whitelist

When to bring us in

If you actively need xmlrpc (legacy apps), restrict via a Cloudflare rule with IP whitelist.

See also

None of the above fits?

Describe your situation below. We pass your input plus the steps you already saw to our AI and return tailored next-step advice. If it's too risky to DIY, we'll say so.

Who are you?

For the AI question we need your email and company, so we can follow up if the AI gets stuck, and to prevent abuse.

Limited to 2 questions per hour and 5 per day, kept lean so the AI stays useful. For more, contacting us directly works better for you and us.

Or skip the DIY entirely

Our Managed IT clients do not look these things up. One point of contact, a fixed monthly price, resolved within working hours.