xmlrpc.php still ships with WordPress core. A front-end that never mentions XML-RPC still has a public endpoint that speaks application passwords, pingbacks, and a long list of wp.* methods.
Turning off pingbacks is not turning off XML-RPC. Deleting a REST plugin is not turning off XML-RPC. xmlrpc.php is a file in the document root until you block it.
Inventory whether the public hostname still answers XML-RPC, and whether any Application Password still works through it.
What xmlrpc.php actually is
WordPress core serves POST /xmlrpc.php as an XML-RPC endpoint. Methods include pingbacks, system.listMethods, and authenticated wp.* / wp.getUsersBlogs style calls. Application Passwords (5.6+) authenticate here as well as on /wp-json/.
You can disable the feature without deleting the file:
add_filter('xmlrpc_enabled', '__return_false');
That filter makes WordPress refuse XML-RPC methods. The file may still 200 with a fault. Blocking at nginx / Apache (return 403 on xmlrpc.php) is the stronger control: the worker never boots WordPress for that POST.
Pingbacks have their own switches (Discussion settings, xmlrpc_methods filter). A site that “doesn’t use pingbacks” often still has XML-RPC on for a mobile app that has since moved to the REST API.
Run this only against a WordPress you own.
Why it stays enabled
The REST API is what current integrations use. xmlrpc.php is leftover from the Jetpack / WordPress app / Windows Live Writer era. Nothing in a default install removes it. Hosts add a WAF rule, then someone puts WordPress behind a new CDN and the rule is on the old origin.
Application Passwords make the leftover worse: a password issued for REST also works on XML-RPC unless you disabled XML-RPC. Revoking REST access in your head does not revoke this path.
The fixture
On a test WordPress you own:
HOST=https://wp.example.org # a host you own
# unauthenticated: does the endpoint speak XML-RPC?
curl -sS -D - -o /tmp/xmlrpc-body.txt \
-H 'Content-Type: text/xml' \
-d '<?xml version="1.0"?>
<methodCall><methodName>system.listMethods</methodName></methodCall>' \
-w "%{http_code}\n" \
"$HOST/xmlrpc.php"
Interpret:
- 403/404/405 from nginx — blocked at the edge. Record which layer.
-
200 + XML fault
XML-RPC services are disabled—xmlrpc_enabledis false. File still reachable. -
200 + XML array of method names — XML-RPC is on.
system.listMethodsworked without a password. -
200 +
wp.getUsersBlogssuccess with an Application Password — authenticated leftover.
Then, with a canary Application Password you issued for this test:
# authenticated call; only on a site you own
# wp.getUsersBlogs is a common fingerprint
curl -sS -o /tmp/xmlrpc-auth.xml \
-H 'Content-Type: text/xml' \
-d "<?xml version=\"1.0\"?>
<methodCall>
<methodName>wp.getUsersBlogs</methodName>
<params>
<param><value>$USER</value></param>
<param><value>$APPLICATION_PASSWORD</value></param>
</params>
</methodCall>" \
"$HOST/xmlrpc.php"
Keep a row:
| Check | Result |
|---|---|
HTTP status of POST /xmlrpc.php
|
|
system.listMethods |
disabled / method list |
| Application Password via XML-RPC | 401 / blogs listed |
| nginx/WAF rule on the public hostname | present / missing |
xmlrpc_enabled filter |
true / false |
Alert when:
- The public hostname returns a method list.
- An Application Password that you issued for REST also succeeds on XML-RPC and XML-RPC is not in the integration’s design.
- The WAF rule exists on the old origin and not on the current CDN hostname.
If you need XML-RPC for one legacy client, restrict it by IP and keep Application Passwords on a dedicated user. If you do not need it, block the file and set the filter. Do both; the filter alone still boots PHP.
What this inventory is not
This is not a REST Application Password offboarding check (that is a separate note). It answers one question: does this WordPress still speak XML-RPC on the public hostname, and can a leftover Application Password use that path.
Disclosure: I work on GuardLMS, a product of Ldesign Media. xmlrpc.php, xmlrpc_enabled, and Application Passwords on XML-RPC are WordPress core behaviour.
Top comments (0)