Plugin Pulse Beta
← Pulse

Disable XML-RPC Pingback

by Samuel Aguilera · Uncategorized

Also makes 13 other plugins · 86.9K+ installs across the portfolio →

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.

Try it live opens a temporary test site in your browser, which can take about 20 seconds to load. Plugins that rely on outside services or a full server may not work completely there.

Health

C 68/100

no flags

Active installs

60K+

≈65K estimated

Momentum

+35%

downloads vs prior 30d

Biggest opportunity: Swap “xml” and “ddos” for “pingbacks” and “abuse”. “xml” isn't earning its slot: it only gets you to #23. “pingbacks” sits at #6 untagged, close enough for a declared tag to move it up. “ddos” isn't earning its slot: it only gets you to #15. “abuse” sits at #17 untagged, close enough for a declared tag to move it up. All five slots are taken, so one has to go.

How scoring works →
68 Health · C
Maintenance 65/100
Rating quality 71/100
Support 70/100

68 health vs 58 average across 25,737 Uncategorized plugins

Install conversion

How it's measured →

14%

of downloads still active

At least 60K of 434.1K lifetime downloads are still running, above its category: the median Uncategorized plugin keeps 0.6%, across 17,770 plugins.

Downloads count every update, not just first installs, so older and more frequently released plugins read lower. Compare against other Uncategorized plugins, not across the directory. wp.org reports active installs as the bottom of a band, so the real rate is this or higher.

This plugin shipped 1 release in the last 12 months, and every existing install that updated counted as another download. wp.org publishes no split between first installs and updates, so we show the raw rate rather than guess at one.

Details

Version
1.2.2
Last updated
11mo ago
Added
2014-03-11 · 12 yrs old
Requires WP
4.8
Tested up to
6.8.12
Requires PHP
5.6

Recent review vibe

read from the latest 12 reviews to 2025-10-21
Mixed PraiseCompatibilityBroken updates

Most reviewers say it does exactly what it promises against XML-RPC pingback attacks and still works years later, though a couple report it didn't block anything on their setup or broke their site.

Directory ranking optimization

How it's scored →

How well this listing is tuned to rank in WordPress.org search, on the factors an owner controls. Not popularity, optimization.

84 / 100

Well optimized

Most to gain: Rating quality

Update recency 73/100

Updated 341 days ago, past the ~180 days where wp.org starts discounting

WP compatibility 100/100

Tested up to WordPress 6.8.12, the current branch or newer

Rating quality 67/100

3.9★ over 14 reviews, smoothed to 4.06★ and held back under 25 reviews

Listing tuning 100/100

5 of 5 tags set · short description in place

To rank higher: Too few reviews to rank on quality — nudge happy users to leave one.

Get the full rank-higher report →

Daily downloads

Since 5 Oct 2022 · 1,488 days · wp.org + Plugin Pulse archive

+35% vs prior 30d
6831 Oct 2026

30-day downloads

Rolling 30-day volume · peak 2.7K · peaks are release surges

2.6K31 Oct 2026

Directory rank vs rivals

wp.org popularity rank over time · higher is better · when a rival's line climbs above yours, they've overtaken you

Disable XML-RPC Ping · #667youSimple XML-RPC Disab · #28038Simple XML-RPC Pingb · #46317

Rating trend

Star average over time · dips mark rough releases

3.931 Oct 2026

Health trend

Composite health score, snapshotted daily

6831 Oct 2026

Update activity

How busy the existing users are, measured as downloads in the last 30 days for every 1,000 active sites. A spike means a new release everyone's pulling; a long, slow decline means an aging user base that updates less.

4331 Oct 2026

Release cadence

Occasionally updated
from wp.org release tags

How often this plugin actually ships. A steady rhythm is the maintenance signal a single "last updated" date can't show.

1

releases in the last 12 months

11mo ago

latest release · v1.2.2 · 24 Nov 2025

5

tagged releases on record

Recent releases

1.2.2 · 24 Nov 20251.2.1 · 14 Nov 20191.2 · 30 Mar 20191.1 · 6 Nov 20171.0 · 3 Oct 2014

What its installed base runs

via wordpress.org

Share of active installs on each version of this plugin · 95% run the current release. Green is the current release; a big slice on older versions is a user base that has stopped updating.

v1.2 95%
Older / other versions 4.8%

Estimated active installs

The public count shows “60K+”. Our estimate pins where the real number sits.

tracked estimate
60K–70K ≈65K

Crossed into this band 2.5 years ago; a band this size takes about a year or more to cross, which places it about 50% of the way through.

Install history since 4 Sep 2019

60K31 Oct 2026

Recent reviews

All reviews on wp.org ↗
  1. ★★★★★ Gordon
    1.0y ago

    The plugin author is still actively engaged with this excellently useful plugin. It receives updates only when needed which might be years in between updates. Still works great! Highly recommend.

    Read on wp.org ↗
  2. ★★★★★ morti037
    5.5y ago

    There is better option than this plugin. I have used disable xmlrpc api and its works fine for me.

    Read on wp.org ↗
  3. ★★★★★ captainzandra
    6.1y ago

    This broke my site, I had to revert to a backup on the server after installing it.

    Read on wp.org ↗
  4. ★★★★★ Fernando Tellado
    9.8y ago

    Gran trabajo Samuel, en combinación con algunas reglas de htaccess hace un trabajo fantástico.

    Read on wp.org ↗
  5. ★★★★★ wplike75
    10.0y ago

    Thank you for this free and great plugin.

    Read on wp.org ↗
  6. ★★★★★ gmyoganand
    10.4y ago

    Does what it says and this is what needed for a XMLRPC attacks. Thanks.

    Read on wp.org ↗
  7. ★★★★★ yolandal
    10.4y ago

    I’m confused here… I see this plugin I’ve never heard of and I never installed… and the bad thing is; I can’t remove it! If this is a security plugin it sure doesn’t behave like it! It’s behaviour is a no-go for me. Update: My hosting provider admittd they have installed this plugin. But they never notified me. So now I’m giving a 5 star rating.

    Read on wp.org ↗
  8. ★★★★★ zoxee
    11.2y ago

    Doesn’t work on 4.2.4. For testing purposes i installed 2 plugins to compare : 1. Disable XML-RPC Pingback from Samuel Aguilera 2. Disable XML-RPC from Philipp Erb When 1 is activated, i am still able to post articles from 3 different applications. When 2 is activated, i get following message in all 3rd party applications : “XML-RPC services are disabled on this site” Samuel, instead of insulting people you should update you plugin.

    Read on wp.org ↗

Latest updates

via wp.org changelog

Recent releases and news for this plugin

  1. — Version 1.2.2 Improved WP version checking to avoid a notice under certain versions of WP. 1.2.2
  2. — Version 1.2.1 Minor changes to make code 100% compliant with WordPress Coding Standards. 1.2.1
  3. — Version 1.2 Added support for X-Pingback header removal in recent versions of WP. 1.2
  4. — Version 1.1 Added code to remove X-Pingback from HTTP headers as suggested by user https://wordpress.org/support/topic/remove-x-pingback-http-header 1.1
  5. — Version 1.0 Initial release. 1.0

Behavioral tests

via WP Hive

Automated install-time checks, tested on PHP 7.4.8 · WP 5.7.2

✓ Low memory footprint
✓ Low page-speed impact
✓ Runs on latest PHP + WP
✓ No PHP errors
✓ No JS errors
✓ Activates cleanly
✓ No resource errors
✓ No external HTTP errors
✓ Optimized database use
✕ Frequently updated

Languages

via translate.wordpress.org

Translated into 15 languages, 15 at 90% or more

Arabic 100%
Dutch 100%
English (South Africa) 100%
English (UK) 100%
Galician 100%
Hungarian 100%
Japanese 100%
Russian 100%
Spanish (Argentina) 100%
Spanish (Chile) 100%
Spanish (Mexico) 100%
Spanish (Spain) 100%
Spanish (Venezuela) 100%
Swedish 100%
Ukrainian 100%

AI assistants

How it's measured →

Whether ChatGPT and Claude name this plugin when asked the category question, and whether the readme gives them something to quote.

Not measured yet for this plugin’s topics. Its tracked searches are not among the measured topics. See the topics measured so far.

Readme readiness

3 of 8 pass · checked 26 Oct 2026

Can an assistant quote this readme? Eight deterministic checks over the wp.org listing, no model involved.

  • ! Says what it does Short description names no action; say what the plugin does for the site.
  • ! Has a FAQ No FAQ section.
  • ! FAQ asks real questions No FAQ to judge.
  • ! Names who it is for Never says who the plugin is for or what they use it for.
  • ✓ Names what it works with Mentions Jetpack.
  • ✓ Headings and lists 2 headings and 3 lists.
  • ! Enough to quote 946 characters of description; under 1,000 there is little to quote.
  • ✓ Tags match the text 4 of 5 tags appear in the text; "ddos" does not.

Growth timeline

Install-tier crossings we have observed, and how long each tier took to outgrow

  1. 2024-05-18 70K+ → 60K+ down after 12 days in tier
  2. 2024-05-06 60K+ → 70K+ up after 84 days in tier
  3. 2024-02-12 70K+ → 60K+ down after 1228 days in tier
  4. 2020-10-02 80K+ → 70K+ down after 1033 days in tier
  5. 2017-12-04 70K+ → 80K+ up after 345 days in tier
  6. 2016-12-24 60K+ → 70K+ up after 104 days in tier
  7. 2016-09-11 40K+ → 60K+ up after 285 days in tier
  8. 2015-12-01 30K+ → 40K+ up

Competes with

The plugins that solve the same job, ranked by shared tags then reach, closest match first. The letter on the right is each plugin's health grade (A best, F worst).

Embed this report card

Drop a live Pulse card for Disable XML-RPC Pingback into a readme, a review or a deck. It updates itself.

<iframe src="https://plugins.wpmayor.com/embed/disable-xml-rpc-pingback" width="480" height="300" style="border:0" loading="lazy" title="Disable XML-RPC Pingback — Plugin Pulse"></iframe>
Preview card ↗

Disable XML-RPC Pingback: 60K+ active installs, 3.9★ (14 reviews). Plugin Pulse (WP Mayor), as of 2026-10-31. https://plugins.wpmayor.com/plugin/disable-xml-rpc-pingback

Spotted a number that looks wrong? Report a data issue and we'll check it against the source.