WordPress XML-RPC Enabled

The WordPress XML-RPC interface (xmlrpc.php) is reachable, giving attackers another login route for password guessing and a pingback function that makes the server fetch addresses they choose.

SeverityLow
CVSS 3.13.7 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N Open in the calculator
CVSS 4.06.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-307: Improper Restriction of Excessive Authentication Attempts
OWASP Top 10A07:2025 Authentication Failures
MITRE ATT&CKT1110.001 Password Guessing, T1110.003 Password Spraying, T1110.004 Credential Stuffing, T1590.005 IP Addresses
CategorySecurity Misconfiguration

Description

The WordPress XML-RPC interface, served at /xmlrpc.php, is enabled and reachable from the internet. XML-RPC lets remote clients, such as publishing apps and plugins including Jetpack, call WordPress functions over HTTP. It is enabled by default and the administration interface offers no setting to turn it off, so it is often left exposed on sites that never use it.

The interface interests an attacker for two reasons. Many of its methods take a user name and password with each call, so it is a second login route through which an attacker can guess, spray or stuff passwords against user accounts, possibly outside the lockout, CAPTCHA, rate limiting and multi-factor controls applied to the normal login page, depending on the plugins in use. Older WordPress releases also accepted hundreds of password attempts in a single request through system.multicall; current releases stop checking passwords within a request once one attempt has failed. A recovered administrator password gives full control of the site and usually of the code it runs, since administrators can install plugins. The risk is lower where every account has a strong, unique password and multi-factor authentication that also covers XML-RPC.

Separately, the pingback.ping method makes the server fetch an address supplied by the caller in order to verify a link. An attacker can use it to make the server send requests to third parties, enlisting the site in attacks on others, and can often learn the server's real IP address when it sits behind a content delivery network or web application firewall, allowing them to bypass it. This risk is lower where no published content accepts pingbacks.

The interface is confirmed by sending a system.listMethods call in a POST request to /xmlrpc.php, which returns the methods available; a GET request returns a short message saying that the server accepts POST requests only. WordPress scanners such as WPScan report the interface as enabled.

Remediation

Disable XML-RPC unless something the organisation relies on needs it:

  • Where nothing uses it, block requests to xmlrpc.php at the web server, reverse proxy or web application firewall, so that WordPress never processes them. Check first whether Jetpack, a mobile publishing app or another remote client depends on it, because blocking the file stops these working.
  • Where XML-RPC must stay available, remove the pingback methods with the xmlrpc_methods filter, restrict access to the addresses of the services that need it where these are known, and make sure login rate limiting and multi-factor authentication apply to XML-RPC as well as to the login page. The xmlrpc_enabled filter only disables methods that require authentication; it does not stop pingbacks.
  • Enforce strong, unique passwords for every account with publishing or administrative rights.
nginx: location = /xmlrpc.php { deny all; } Apache 2.4 (virtual host or .htaccess): <Files xmlrpc.php> Require all denied </Files> WordPress (a small plugin), keeping XML-RPC but removing pingbacks: add_filter( 'xmlrpc_methods', function ( $methods ) { unset( $methods['pingback.ping'], $methods['pingback.extensions.getPingbacks'] ); return $methods; } );

Confirm the fix by sending a system.listMethods request to /xmlrpc.php and checking that it is refused or, where XML-RPC is kept, that the pingback methods are no longer listed.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Web Applications Findings

Every Web Applications finding