Skip to main content
LowAPIOWASP A05:2021CWE-611

How to fix: XML-RPC endpoint referenced

A page references an XML-RPC endpoint (e.g. xmlrpc.php). In WordPress and similar CMSes this legacy endpoint enables brute-force amplification attacks and remote method invocation when it's actually reachable and un-hardened.

Why it matters

WordPress xmlrpc.php allows an attacker to test thousands of username/password combinations in a single HTTP request using system.multicall: a brute-force amplification attack. It also enables pingback-based SSRF and DDoS amplification against third-party hosts.

XML-RPC is a legacy remote procedure call protocol used by WordPress for the mobile app and Jetpack. When left publicly accessible it enables brute-force amplification (one request = thousands of auth attempts), pingback SSRF, and remote content modification.

How to fix it

  1. 1In WordPress: disable xmlrpc.php unless specifically required by a plugin or mobile app
  2. 2Block xmlrpc.php at the web server or WAF level for non-WordPress applications
  3. 3Use a security plugin (Wordfence, iThemes Security) to block XML-RPC at the application level

Code examples

Nginx: block xmlrpc.php

nginx
location = /xmlrpc.php {
    deny all;
    return 403;
}

Apache: block xmlrpc.php

APACHE
<Files xmlrpc.php>
    Order Deny,Allow
    Deny from all
</Files>

WordPress: disable XML-RPC via filter

PHP
// In functions.php or a must-use plugin
add_filter('xmlrpc_enabled', '__return_false');

add_filter('xmlrpc_methods', function($methods) {
    unset($methods['pingback.ping']);
    unset($methods['pingback.extensions.getPingbacks']);
    return $methods;
});

References

Detected automatically by VulnRadar. The check id is xml-rpc, stable across every scan so you can filter or diff on it.

See every api check

Questions

How severe is XML-RPC endpoint referenced?
VulnRadar rates this low severity in the api category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
Does VulnRadar check for this automatically?
Yes. It runs as part of every scan under the check id xml-rpc, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does XML-RPC endpoint referenced map to?
It maps to CWE-611. In the OWASP Top 10 it falls under A05:2021.

Missing a check?

The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.

Propose a checkHow a check is built

Scan your own site for xml-rpc endpoint referenced

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: XML-RPC endpoint referenced | VulnRadar