Plugin profile · observed daily since 02 Aug 2026
Disable XML-RPC-API
Active installs100,000+ rounded
Current authorAmin Nazemi
Owner changesNone while we have been watching
Last release7 months ago 04 Feb 2026
Support0 / 1 resolved, last 2 months
Releases on record23
Rating4.2 /5 · 43
Added to directory01 Oct 2020
Requires WP5.0
Requires PHPfalse
Version lag0.2 behind
Tested up toWP 6.9.7 WordPress is now on 7.1
PluginPedia reports published data and observable changes. It does not rate plugin quality or safety, infer intent, or make recommendations. These are observations rather than a verdict. How this works
Ownership
Held by Amin Nazemi throughout, with no change of ownership observed since daily tracking began on 02 Aug 2026.
Full observed history, including every field transition
Committing accounts
Read from the plugin’s public release log, so these predate this registry. A committing account is not an owner. Thirty accounts commit to WooCommerce and it has never changed hands.
| Account | Releases | First | Last |
|---|---|---|---|
| aminnz | 23 | 15 Dec 2020 | 04 Feb 2026 |
This registry did not observe a transfer; it read these names off a public log. Whether that reflects a change of ownership is not something the directory publishes.
Adoption
How widely the plugin is installed, and what the people running it think of it. WordPress.org rounds install figures to one significant digit, so they describe an order of magnitude rather than a headcount.
Very widely adopted: 100,000+ active installs. In the top tier of the directory by install count.
182 downloads a day over the last 7 days, steady against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
08 Aug 2026peak 311/day07 Sep 2026
Daily record
Every field we record, one column per observation. Fields that never moved are named once rather than repeated across every column. A row of identical numbers would be padding.
| Field | 25 Aug | 26 Aug | 27 Aug | 28 Aug | 29 Aug | 30 Aug | 31 Aug | 01 Sep | 02 Sep | 03 Sep | 04 Sep | 05 Sep | 06 Sep | 07 Sep |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 251 | 245 | 204 | 191 | 150 | 113 | 200 | 190 | 213 | 311 | 181 | 181 | 0 |
| Support threads | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 0 | 1 | 1 | 1 | 1 | 1 |
Unchanged throughout: ratings total (43) · active installs (100,000+) · version (2.1.7) · threads resolved (0)
37 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Added to directory5.5 years ago 01 Oct 2020
Requires WP5.0
Requires PHPfalse
Version lag0.2 behind
Is anyone still maintaining this?
- Last released 04 Feb 2026, 216 days ago.
- Declares compatibility only up to WordPress 6.9.7, while 7.1 is current. The author has not confirmed it runs on the last 2 releases.
- 0 of 1 support threads answered in the last two months.
- The same account maintains 4 other plugins, and none has been updated in over a year, the most recent on 23 Apr 2025.
A plugin that does one thing correctly may need no changes for years; a long gap is not, by itself, evidence of neglect.
History
Everything dated that this registry holds about the plugin, most recent first. Releases carry the author’s own release date; everything else is dated to when it was observed.
Entries marked from the release log predate this registry, and daily observation began 02 Aug 2026. They were read from the plugin’s public SVN history after the fact, not watched as they happened. Everything else was observed directly.
- 02 Aug 20261 month agoFirst observed by PluginPediaDaily snapshots of this plugin’s directory record begin here. Everything above this line is observed; anything before it comes from fields the API itself reports.
- 04 Feb 20267 months agoVersion 2.1.7 released
- 28 Nov 202421 months agoVersion 2.1.6 releasedfrom the release logCommitted by aminnz.
- 20 Apr 20242 years agoVersion 2.1.5 releasedfrom the release logCommitted by aminnz.
- 13 Aug 20233 years agoVersion 2.1.4.8 releasedfrom the release logCommitted by aminnz.
- 13 Aug 20233 years agoVersion 2.1.4.9 releasedfrom the release logCommitted by aminnz.
- 12 Feb 20233.5 years agoVersion 2.1.4.7 releasedfrom the release logCommitted by aminnz.
- 06 Nov 20223.5 years agoVersion 2.1.4.5 releasedfrom the release logCommitted by aminnz.
- 17 Sep 20223.5 years agoVersion 2.1.4.4 releasedfrom the release logCommitted by aminnz.
- 22 Aug 20224 years agoVersion 2.1.4.1 releasedfrom the release logCommitted by aminnz.
- 22 Aug 20224 years agoVersion 2.1.4.3 releasedfrom the release logCommitted by aminnz.
- 21 Aug 20224 years agoVersion 2.1.4 releasedfrom the release logCommitted by aminnz.
- 04 Jun 20224 years agoVersion 2.1.3 releasedfrom the release logCommitted by aminnz.
- 30 Jan 20224.5 years agoVersion 2.1.2 releasedfrom the release logCommitted by aminnz.
- 15 Dec 20205.5 years ago10 earlier releasesfrom the release logBetween 15 Dec 2020 and 22 Jul 2021. Listed individually in the public release log rather than here.
- 01 Oct 20205.5 years agoAdded to the WordPress.org directoryReported by the plugin API as the date this plugin was added.
What we know, and what we don’t
Everything on this page in one place, including the gaps, so that nothing here is mistaken for a clean bill of health.
What we know
- It has been held by Amin Nazemi for all 37 days we have observed it.
- It was last released 7 months ago (04 Feb 2026).
- Its author declares it tested up to WordPress 6.9.7; WordPress is now on 7.1.
- WordPress.org reports 100,000+ active installs.
- It carries 43 ratings, averaging 4.2 out of 5.
- 0 of 1 support threads in the last two months are marked resolved.
Every record on this site, this one included, works under the same limits. We read what WordPress.org publishes about a plugin, never the plugin’s own code, so nothing here says whether a plugin is well built or safe. Install counts reach us already rounded; a change smaller than a band step doesn’t show. We don’t track security advisories yet. For anything older than our first observation we rely on the plugin’s public release log, where one exists. What this registry can and cannot see
Similar plugins
Plugins that share this one’s tags and talk about the same things in their own descriptions. Distinctive tags count for far more than broad ones. Sharing hover means something, sharing woocommerce does not, and a plugin that never mentions the subject matter is left out however its author tagged it. Among close matches, more widely installed plugins are listed first. This is a grouping rather than a ranking of quality.
Simple Disable XML-RPC | Reduce Brute Force & DDOS Attacks
Simply disable XML-RPC on your WordPress site with a simple toggle switch. Protect your site from XML-RPC attacks and improve security.
1,000+ installs5.0★ (5)updated 09 Nov 2025
far fewer installs
Compare side by side Disable XML-RPC Pingback
Stops abuse of your site's XML-RPC by simply removing some methods used by attackers. While you can use the rest of XML-RPC methods.
60,000+ installs3.9★ (14)updated 24 Nov 2025
Compare side by side Remove & Disable XML-RPC Pingback
Prevent pingback, XML-RPC and denial of service DDOS attacks by disabling the XML-RPC pingback functionality.
8,000+ installs3.0★ (6)updated 24 Jul 2023
far fewer installs · no release in over 18 months
Compare side by side Eazy XMLRPC Pingback Disable
This plugin disables the WordPress XMLRPC pingback ping.
700+ installs5.0★ (4)updated 02 Jan 2018
far fewer installs · no release in over 18 months
Compare side by side Stop XML-RPC Attacks
Blocks dangerous XML-RPC methods while preserving Jetpack, WooCommerce, and mobile apps compatibility.
6,000+ installs5.0★ (4)updated 27 Aug 2026
far fewer installs
Compare side by side WP Login Door
Adds a secret URL key to access the login page and lets you disable XML-RPC, protecting against bruteforce attacks.
400+ installs5.0★ (6)updated 11 Jun 2025
far fewer installs
Compare side by side Grouped from the tags each author chose for their own plugin, so the grouping is only as good as those tags.
Reach out about this record
Corrections, missing context, or anything else about Disable XML-RPC-API: a person reads every submission, and corrections get a reply within 5 business days.