=== Manage XML-RPC ===
Contributors: brainvireinfo
Donate link: http://www.brainvire.com
Tags: security, xmlrpc.php attack, brute force attacks, xml-rpc pingback, block xml-rpc
Requires at least: 4.0
Tested up to: 6.7.1
Stable tag: 1.0.2
License: GPLv2 or later
License URI: http://www.gnu.org/licenses/gpl-2.0.html

Enable/Disable XML-RPC for all or based on IP list, also you can control pingback and Unset X-Pingback from HTTP headers.

== Description ==

You can now disable XML-RPC to avoid Brute force attack for given IPs or can even enable access for some IPs. XML-RPC on WordPress is actually an API that gives developers who build mobile apps, desktop apps and other services, the ability to talk to a WordPress site. The XML-RPC API that WordPress provides gives developers, a way to write applications (for you) that can do many of the things that you can do when logged into WordPress via the web interface.

= Features =

Block XML-RPC by following way.

* Disable pingback.ping, pingback.extensions.getPingbacks and Unset X-Pingback from HTTP headers, that will block bots to access specified method.
* Disable/Block XML-RPC for all users.

== Installation ==

1. Upload the plugin files to the `/wp-content/plugins/` directory, or install the plugin through the WordPress plugins screen directly.
2. Activate the plugin through the 'Plugins' screen in WordPress
3. Use the 'XML-RPC Settings' screen to configure the plugin.



== Frequently Asked Questions ==

= Do I need to take a backup of my existing .htaccess file =

Yes, it's preferable to take a backup of existing .htaccess file. 

= What if .httaccess file doesn't have writeable permission? =

You can copy and paste new rule in your .htaccess file from plugin setting page.

== Screenshots ==

1. screenshot-1.png

== Changelog ==

= 1.0.2 =
1. Fixed bugs and conducted compatibility checks with the latest WordPress version 6.7.1.
2. Resolved warnings and errors identified during the compatibility assessment.

= 1.0.1 =
* Beta release with basic testing.