| 开发者 | nextdoorentertainment |
|---|---|
| 更新时间 | 2026年6月26日 20:00 |
| PHP版本: | 7.0 及以上 |
| WordPress版本: | 7.0 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
<meta name="generator"> tag, feed generators and the WLW manifest.?ver=) on enqueued CSS/JS, and the same inside inline CSS.<body> tag (e.g. page-builder version classes).<meta name="generator"> tags.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.readme.html / license.txt, and the install.php / upgrade.php setup pages (blocked for non-logged-in visitors so admins can still run updates).system.multicall.wp-cron.php (with an optional secret token for your system cron)./wp-json/wp/v2/users endpoint.?author=N redirect that leaks usernames..htaccess rules — the site returns to its normal state.
version-cloak folder to /wp-content/plugins/, or install the ZIP via Plugins → Add New → Upload Plugin.No. It hides or decoys version information to reduce automated scanning. The actual fix for an outdated component is to update it. Use this as an additional layer.
Obfuscate removes or blocks the version so a scanner reports "could not determine the version". Decoy reports a plausible current version so the site reads as fully up to date. Use a real, recent version for Decoy — an implausible value may be ignored by scanners.
WordPress detects updates from each component's real version (its main file header for plugins, style.css for themes), which is read independently. Core and plugin update notifications are unaffected. Masking a theme's style.css version does affect that theme's own update notice, so the plugin shows its own update notice in that case.
Almost always page caching. Purge your cache (e.g. LiteSpeed → Purge All) and any CDN after saving.