Turn on Vulnerability alerts in Settings to see which installed plugins and themes have known vulnerabilities. It is off until you turn it on. Settings, 2FA, and connection details are preserved.<\/p>","0.6.52":"
Connected sites now check comments against a shared spammer list; turn it off in Settings. Failed logins count against the account they tried, and signing in clears only that account's failures. Settings, 2FA, and connection details are preserved.<\/p>"},"ratings":[],"assets_icons":{"icon-128x128.png":{"filename":"icon-128x128.png","revision":3706552,"resolution":"128x128","location":"assets","locale":"","width":128,"height":128},"icon-256x256.png":{"filename":"icon-256x256.png","revision":3706552,"resolution":"256x256","location":"assets","locale":"","width":256,"height":256},"icon.svg":{"filename":"icon.svg","revision":3706552,"resolution":false,"location":"assets","locale":false}},"assets_banners":{"banner-1544x500.png":{"filename":"banner-1544x500.png","revision":3706552,"resolution":"1544x500","location":"assets","locale":"","width":1544,"height":500},"banner-772x250.png":{"filename":"banner-772x250.png","revision":3706552,"resolution":"772x250","location":"assets","locale":"","width":772,"height":250}},"assets_blueprints":{},"all_blocks":[],"tagged_versions":["0.6.46","0.6.47","0.6.48","0.6.49","0.6.50","0.6.51","0.6.52","0.6.53"],"block_files":[],"assets_screenshots":{"screenshot-1.png":{"filename":"screenshot-1.png","revision":3726860,"resolution":"1","location":"assets","locale":"","width":1440,"height":1100},"screenshot-2.png":{"filename":"screenshot-2.png","revision":3726860,"resolution":"2","location":"assets","locale":"","width":1440,"height":1100},"screenshot-3.png":{"filename":"screenshot-3.png","revision":3726860,"resolution":"3","location":"assets","locale":"","width":1440,"height":1100},"screenshot-4.png":{"filename":"screenshot-4.png","revision":3726860,"resolution":"4","location":"assets","locale":"","width":1440,"height":1100}},"screenshots":{"1":"Protection active on an unconnected WordPress installation, with optional two-factor, crawler, and account setup.","2":"Per-crawler AI policies: choose which recognized crawlers are allowed or blocked.","3":"Login limits, two-factor setup links, and a custom login address in one place.","4":"File integrity and malware scan controls, with unscanned state shown accurately."}},"plugin_section":[],"plugin_tags":[246479,13859,247966,276451,9374],"plugin_category":[54],"plugin_contributors":[281942],"plugin_business_model":[],"class_list":["post-365458","plugin","type-plugin","status-publish","hentry","plugin_tags-ai-crawlers","plugin_tags-bot-blocker","plugin_tags-gptbot","plugin_tags-ip-blocklist","plugin_tags-limit-login-attempts","plugin_category-security-and-spam-protection","plugin_contributors-witenlabs","plugin_committers-witenlabs"],"banners":{"banner":"https:\/\/ps.w.org\/witen-blocker\/assets\/banner-772x250.png?rev=3706552","banner_2x":"https:\/\/ps.w.org\/witen-blocker\/assets\/banner-1544x500.png?rev=3706552","banner_rtl":false,"banner_2x_rtl":false},"icons":{"svg":"https:\/\/ps.w.org\/witen-blocker\/assets\/icon.svg?rev=3706552","icon":"https:\/\/ps.w.org\/witen-blocker\/assets\/icon.svg?rev=3706552","icon_2x":false,"generated":false},"screenshots":[{"src":"https:\/\/ps.w.org\/witen-blocker\/assets\/screenshot-1.png?rev=3726860","caption":"Protection active on an unconnected WordPress installation, with optional two-factor, crawler, and account setup."},{"src":"https:\/\/ps.w.org\/witen-blocker\/assets\/screenshot-2.png?rev=3726860","caption":"Per-crawler AI policies: choose which recognized crawlers are allowed or blocked."},{"src":"https:\/\/ps.w.org\/witen-blocker\/assets\/screenshot-3.png?rev=3726860","caption":"Login limits, two-factor setup links, and a custom login address in one place."},{"src":"https:\/\/ps.w.org\/witen-blocker\/assets\/screenshot-4.png?rev=3726860","caption":"File integrity and malware scan controls, with unscanned state shown accurately."}],"raw_content":"\n
You decide who gets into your WordPress site. Choose which AI crawlers can read your content, lock out bots guessing your password, and stop comment spam. Protection starts the moment you activate it, with no account and no setup wizard.<\/p>\n\n
Every recognized crawler gets its own allow or block switch. Welcome every AI crawler, block them all, or pick one by one. Nothing is blocked until you choose.<\/p>\n\n
Witen Blocker recognizes GPTBot, ChatGPT-User, OAI-SearchBot, ClaudeBot, PerplexityBot, Common Crawl, Meta-ExternalAgent, Amazonbot, and Applebot, plus the major search engines and ten uptime monitors, so a rule for one bot never catches the services you rely on.<\/p>\n\n
robots.txt states your preference; Witen Blocker enforces it. A crawler you block gets an HTTP 403. Crawlers are matched by their published network ranges as well as their user agent, so a scraper pretending to be Googlebot doesn't get Googlebot's pass.<\/p>\n\n
Five failed logins in five minutes locks the address out for an hour, and you can change all three numbers. Add two-factor sign-in with any authenticator app and printable recovery codes, so a stolen password alone no longer opens your dashboard. Move the login page to an address only you know.<\/p>\n\n
Template traversal and comment exploit requests are refused before they reach the vulnerable WordPress code. No account needed.<\/p>\n\n
A hidden field and a timing check catch bots. No comment text ever leaves your site.<\/p>\n\n
Connected sites can also use a separate shared spammer list for comments. Repeated honeypot detections from different sensors and customer licenses can contribute addresses to this list. Timing checks and hits on the shared list do not contribute new shared reputation. Comments marked as spam remain in the Spam folder for review. This protection does not create login or site-wide blocks; you can turn it off in Witen > Settings<\/strong>.<\/p>\n\n A daily scan checks WordPress core against the official checksums, flags new and changed files, and looks for known malware patterns. Nothing is deleted or changed without you. Connected sites also receive maintained malware catalogs.<\/p>\n\n Connect a free Witen account and your site gets blocklists built from attacks seen across every Witen site and server. An address caught attacking other sites is blocked on yours before it tries. Requests are checked against a local copy of the list, so no page load waits on Witen.<\/p>\n\n Connecting requires a Witen account and security-event sharing. Every local feature stays free, with no trial expiry. Free connected sites get a daily blocklist update. Paid plans add more sites and servers, other feed profiles, and off-site backup storage.<\/p>\n\n On shared hosting, blocked requests get an HTTP 403 from WordPress, with no server access needed. On your own Linux server, add the Witen Warden agent and blocks move to the firewall, before the traffic ever reaches PHP.<\/p>\n\n Get started:<\/strong> activate Witen Blocker and open Witen > Dashboard<\/strong> to see what's already on. Use Firewall > Bots and AI crawlers<\/strong> to choose which crawlers can visit, and Login<\/strong> to set up two-factor sign-in.<\/p>\n\n Setup guide<\/a> | Witen plans<\/a> | Support<\/a><\/p>\n\n Connected features use Background sync sends events and site details (listed below) and retrieves blocklists, bot identities, signed malware catalogs, Tor exit nodes, allowlists, service status, network statistics, and feed profiles. Profile changes send your selection and site identifier; IP lookups send the queried address. Block reports include the IP, rule, outcome, request context, and site identifier.<\/p>\n\n Witen terms<\/a> | Witen privacy policy<\/a><\/p>\n\n Enrolled sites refresh Cloudflare terms<\/a> | Cloudflare privacy policy<\/a><\/p>\n\n Integrity scans request official hashes from WordPress.org privacy policy<\/a><\/p>\n\n The plugin does not remotely load executable code or frontend assets. Bundled bot references cause no remote requests or crawler DNS lookups. Collector connections use your DNS resolver. Background jobs and Apache rule checks call your own WordPress URLs.<\/p>\n\n Events stay local until enrollment or explicit Warden socket configuration. Earlier events are never uploaded retroactively. Connected intelligence requires event sharing. Deactivate the plugin to stop reporting from WordPress; a separately running Warden keeps its own reporting configuration.<\/p>\n\n What is shared:<\/strong> IP addresses; successful and failed logins; XML-RPC, comment, registration, and 404 events; request URLs, methods, User-Agent strings, referrers, and query information; and attempted usernames, which may be email addresses. Installation reports include site name and URL, WordPress\/PHP\/plugin versions, and a random installation identifier. An observed IP is not necessarily an attacker. Reports help identify distributed attacks, relate failed logins to later successful ones, and maintain blocklists.<\/p>\n\n Event reports exclude form bodies, post content, comment text, password fields, cookies, and session data. URLs and metadata can contain personal data. File samples and .htaccess backups are separate options, described above. Local storage:<\/strong> the delivery queue holds up to 500 events for seven days. Witen also keeps the latest 100 dashboard events and blocks, block and allow lists, and health counters. Rejected events and block-decision reports have separate diagnostic queues, each limited to 100 records or 1 MiB. Older records are removed at the limit; diagnostics otherwise remain until uninstall.<\/p>\n\n Deactivation preserves settings and existing .htaccess and Warden firewall rules. Uninstall removes Witen options, transients, scheduled actions, and database tables. Collector retention follows its operator's privacy policy; request collector-side deletion from that operator.<\/p>\n\n\n See the setup guide<\/a> to connect a local Warden agent or configure your site through wp-config.php.<\/p>\n\n\n robots.txt states your preference, and crawlers that honor it follow it. Witen Blocker enforces your choice: a crawler you block gets an HTTP 403, and a crawler you allow passes. Use both if you like.<\/p><\/dd>\n Everything local: AI crawler and bot controls, login lockout, two-factor sign-in, comment spam checks, exploit blocks, file and malware scans, and the .htaccess editor. A Witen account adds shared blocklists and reporting.<\/p><\/dd>\n No. Request checks use local data and never wait on a remote service. Blocklist updates, reporting, and scans run in background jobs.<\/p><\/dd>\n Yes. If both plugins handle two-factor, login limits, bot rules, or .htaccess, turn each feature on in one plugin only, then test your login.<\/p><\/dd>\n Open Witen > Login > Login lockout<\/strong> to set the failure window, failure count, and ban duration. Defaults are 5 failures in 5 minutes and a 1-hour ban. Saved settings override Keep your 2FA recovery codes. If you lock yourself out, wait for the ban to expire or follow the recovery guide<\/a>, which covers WP-CLI and SFTP. Deactivating the plugin leaves existing .htaccess and Warden firewall rules in place; the guide shows how to remove them.<\/p><\/dd>\n No. A finding is a file worth a look, and legitimate customizations can trigger one. Witen Blocker shows you which files to check. It doesn't clean an infected site for you.<\/p><\/dd>\nCatch unexpected file changes<\/h4>\n\n
Block attackers before they reach you<\/h4>\n\n
Shared hosting or your own server<\/h4>\n\n
External Services<\/h3>\n\n
Witen Collector<\/h4>\n\n
https:\/\/collector.witenlabs.com<\/code>. Enrollment exchanges your setup token and installation identity for a credential. Witen processes shared reports to identify distributed attacks and provide threat intelligence.<\/p>\n\n\n
WITEN_SEND_MALWARE_SAMPLES<\/code> to boolean true<\/code> in wp-config.php<\/code> permits file-content uploads. Scans do not require them.<\/li>\nWITEN_COLLECTOR_URL selects another collector if you operate one; its operator's policies apply. Explicitly configuring `WITEN_SOCKET_PATH` authorizes sharing with local Warden, whose configuration controls onward delivery. Detecting a socket alone does not enable sharing.\n<\/code><\/pre>\n\nCloudflare proxy ranges<\/h4>\n\n
https:\/\/www.cloudflare.com\/ips-v4\/<\/code> and https:\/\/www.cloudflare.com\/ips-v6\/<\/code> during background maintenance to recognize trusted proxies. Offline sites use bundled ranges. Requests send ordinary HTTPS network metadata, not WordPress visitor events or account data.<\/p>\n\nWordPress.org core checksums<\/h4>\n\n
https:\/\/api.wordpress.org\/core\/checksums\/1.0\/<\/code>, sending your WordPress version, locale, and ordinary HTTPS network metadata. No visitor events, account data, or site content is sent.<\/p>\n\nPrivacy Policy<\/h3>\n\n
WITEN_NO_TELEMETRY<\/code> stops daily installation reports, but not connected security-event sharing.<\/p>\n\n\n
\n
How is this different from robots.txt?<\/h3><\/dt>\n
What can I use without an account?<\/h3><\/dt>\n
Will it slow down my site?<\/h3><\/dt>\n
Can I use it alongside another security plugin?<\/h3><\/dt>\n
How do I change login limits or recover from a lockout?<\/h3><\/dt>\n
WITEN_LOGIN_WINDOW_SEC<\/code>, WITEN_LOGIN_MAX_FAILURES<\/code>, and WITEN_LOGIN_BAN_SEC<\/code> in wp-config.php. Every failure from an address counts toward its ban. Signing in clears only the failures against your own account and never lifts a ban.<\/p>\n\nDoes a scan finding mean my site is hacked?<\/h3><\/dt>\n