Active installations10Adoption 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 Version Cloak version 1.0.4 as active, updated 4mo ago and tested up to WordPress 7.0.
Overview
About this plugin
Version Cloak is a hardening plugin that reduces the information opportunistic, automated scanners can read about your site. Version-matching bots fingerprint a site, look up known issues for the detected versions, and probe the easy targets first. This plugin shrinks that fingerprint.
Important: this plugin obscures version and endpoint information. It does not patch vulnerable code. Keep your plugins, themes, and WordPress core updated — obscurity is a complement to patching, not a replacement for it.
Two version modes (per dropdown)
For WordPress core and for plugins & themes, choose one of:
Off — leave the real version visible.
Obfuscate — remove or block the version so it can’t be read.
Decoy — report a plausible current version (auto-detected latest, or a value you set) so the site reads as up to date.
What it covers
The WordPress <meta name="generator"> tag, feed generators and the WLW manifest.
Version query strings (?ver= ) on enqueued CSS/JS, and the same inside inline CSS.
Version classes on the <body> tag (e.g. page-builder version classes).
Plugin-emitted <meta name="generator"> tags.
Plugin version strings in HTML comments (e.g. SEO plugins).
Static version files served directly by the web server — readme.txt, changelog.txt, release_log.html — and version banner comments in CSS/JS assets. In Obfuscate these are blocked (Apache/LiteSpeed.htaccess, or an Nginx rule you add); in Decoy their version strings are rewritten and automatically reverted when you switch back.
WordPress core readme.html / license.txt, and the install.php / upgrade.php setup pages (blocked for non-logged-in visitors so admins can still run updates).
Other hardening
XML-RPC — disable and return 404, or keep it but remove pingback and system.multicall.
WP-Cron — disable the HTTP pseudo-cron and block external hits to wp-cron.php (with an optional secret token for your system cron).
REST user enumeration — block the anonymous /wp-json/wp/v2/users endpoint.
Author enumeration — block the?author=N redirect that leaks usernames.
Reversible
htaccess rules — the site returns to its normal state.
WordPress.org metadata
Plugin tags
Topics listed for this plugin in the WordPress.org directory.
wp cron
xml rpc
hardening
security
version
Compatibility & maintenance
Compatibility & maintenance
Tested up to WordPress 7.0
Not yet marked as tested with WordPress 7.1. WordPress.org currently lists Tested up to 7.0.
Current WordPress releaseWordPress 7.1
WordPress.org Tested up to7.0
Minimum requirementsWordPress 5.0 · PHP 7.0
Update activity26 Jun 20264mo 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.
