WordPress plugin intelligence profile

EnumGuard

Stops WordPress user enumeration through author URLs, REST, login errors, XML-RPC, sitemaps, and oEmbed.

WP PlugIndex snapshot

Current directory snapshot

Tested up to WordPress 7.1
Current version1.0.0
WordPress coverageTested up to WordPress 7.1
Minimum stackWP 6.3 · PHP 7.4
Directory statusactive
Last directory update19 Sept 20261mo ago
Active installations30Adoption metric — not a quality score
WordPress.org ratingNo WordPress.org ratings yet
Official packageDirect from WordPress.org

Repository metrics are context, not quality scores. Active installations measure adoption and can strongly reflect a plugin’s age and historical popularity. Ratings, recent updates and “Tested up to” metadata also do not guarantee modern code, error-free operation, security, feature completeness or suitability for a particular site. Why active installs don’t tell the whole story →

WP PlugIndex currently records EnumGuard version 1.0.0 as active, updated 1mo ago and tested up to WordPress 7.1.

Overview

About this plugin

EnumGuard is a focused WordPress plugin that stops attackers from confirming that a username or user ID exists. WordPress still prints those signals by default; EnumGuard closes the usual paths without hiding display names on posts.

Under Settings → EnumGuard you get three tabs:

  • Protections — overview of which discovery paths are closed
  • Settings — toggles and custom login / reset messages
  • About — plugin info

Protections covered:

  • Author ID queries (?author=1 ) that would otherwise redirect to the author archive
  • Author archives and their feeds
  • Author archive links printed in HTML
  • author-{id} / author-{nicename} body, post, and comment CSS classes
  • Core users sitemap ( /wp-sitemap-users-1.xml )
  • Unauthenticated /wp-json/wp/v2/users (including?rest_route= )
  • REST _embed author payloads and author link headers
  • Login error messages that distinguish “bad username” from “bad password”
  • Lost-password responses (same confirmation whether the account exists)
  • oEmbed author_url / author_name
  • XML-RPC user-listing methods, with an optional full XML-RPC disable
  • Author sitemaps and author archive URLs from Yoast, Rank Math, and The SEO Framework

Recommended protections ship enabled. Gutenberg still reaches the users REST API for logged-in editors. Display names stay visible.

Login and reset protections also cover WooCommerce forms when WooCommerce is active. XML-RPC can be turned off completely if you do not need Jetpack, pingbacks, or the WordPress mobile app.

WordPress.org metadata

Plugin tags

Topics listed for this plugin in the WordPress.org directory.

  • rest api
  • user enumeration
  • xml rpc
  • login
  • security
Compatibility & maintenance

Compatibility & maintenance

Tested with WP 7.1

Marked as tested with the current WordPress 7.1 release.

Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.1
Minimum requirementsWordPress 6.3 · PHP 7.4
Update activity19 Sept 20261mo ago

“Tested up to” is directory metadata supplied by the plugin author. WP PlugIndex does not turn an older declaration into a claim that the plugin is incompatible.

Changes recorded by WP PlugIndex

Recent tracked changes

No tracked version or compatibility changes have been recorded by WP PlugIndex yet.

Tracking & source

WP PlugIndex tracks public WordPress.org directory metadata and records selected version, compatibility and availability changes as they are detected.

Plugin watchlist

Watch this plugin

Sign in to your WP PlugIndex account or create a free account. Free accounts can watch up to 5 plugins and see what changed.

Watch limit

Watchlist limit reached

You have reached your current active watch limit.