CyberPulse — Erweiterte Sicherheit und Schutz vor Bots

Beschreibung

🛡️ CyberPulse (Cyber Pulse) is a powerful security firewall with IP blocking and whitelist that protects your website 24/7.

Every request is analyzed in real time. Bots, scanners, and attackers are blocked instantly — before they reach your site. The plugin detects suspicious behavior, blocks AI data collectors like GPTBot and ClaudeBot, and stops brute force attacks with automatic IP bans.

Why Choose Cyber Pulse:

  • ⚡ Echtzeitschutz — überwacht jede Anfrage und blockiert Bedrohungen sofort
  • 🍃 Lightweight & Fast — minimal database load, logs stored in files with automatic cleanup
  • 🌍 10 Languages — Russian, English, German, French, Italian, Spanish, Portuguese, Chinese, Japanese, Korean
  • 🚀 Easy to Use — install and protect your site in under a minute
  • 🚫 Clean Interface — no third-party ads; a single, non-intrusive link to the optional PRO edition
  • 🔗 Works with Caching — compatible with WP Rocket, W3 Total Cache, LiteSpeed Cache, and CDN services

Schutzfunktionen:

  • 🤖 AI Scraping Protection — blocks GPTBot, ClaudeBot, PerplexityBot, CCBot, and other AI data collectors
  • 🛡️ .htaccess-Schutz auf Serverebene — optionale (Opt-in) Blockierung sensibler Dateien und KI-Bots direkt auf Apache/LiteSpeed-Ebene
  • 🔍 Multi-layer bot detection (20+ independent checks: User-Agent, HTTP headers, Referer, Accept-Language, behavioral analysis, and more)
  • 🔐 Brute force protection — counts only real login POSTs and escalates through a punishment ladder: temporary block one-week IP ban subnet ban only after a confirmed mass attack
  • ⚖️ Weighted bot score with a challenge band — weak signals together lead to a proof-of-work check instead of an outright ban, so corporate VPNs and privacy relays are not treated as bots
  • 🧩 Verified-crawler table — every crawler User-Agent is bound to the domains and network (ASN) it may come from, so a forged „Googlebot“ fails even with a matching reverse DNS name
  • 🌍 IP Management — block IPs, subnets (/24), whitelist trusted addresses, detect visitor country by IP
  • 📁 WordPress system files hiding — blocks access to wp-config.php, .env, .git, and other sensitive files
  • ⏱️ Rate Limiting — configurable request limits to prevent DDoS and aggressive scraping
  • ✅ IP Whitelist — manual and automatic (server IP, search engines, administrator IPs)
  • 🔒 HTTPS-Weiterleitung erzwingen — automatische 301-Weiterleitung von HTTP zu HTTPS mit Schutz vor Proxy-Schleifen
  • 🛡️ XSS attack protection — blocks cross-site scripting in requests
  • 🔎 404 scanner detection — blocks vulnerability scanners by excessive 404 errors
  • 🔒 URL Firewall — manual path blocking for specific endpoints
  • 👤 User-Agent blacklist with statistics — block specific bots by User-Agent
  • 🔗 Referer verification — blocks suspicious requests without proper Referer header
  • 📊 Security score dashboard — hourly attack histogram, fix recommendations
  • 📧 E-Mail-Benachrichtigungen bei Angriffsspitzen
  • 📝 Event audit log — track logins, settings changes, and plugin activity
  • 🎨 Dunkles und helles Theme für das Adminpanel

Externe Dienste

Dieses Plugin verbindet sich mit externen Diensten, um bestimmte Funktionalitäten bereitzustellen.

🌍 IP Geolocation
* Service: ip-api.com (primary), with ipwho.is and ipapi.co as fallbacks
* Purpose: Determines the visitor’s country for the statistics columns
* Data sent: Visitor IP address
* When: When a request is blocked and the country is not cached yet, and from the background queue (WP-Cron). Results are cached; a failed lookup is retried after 15 minutes.
* Terms of Service: https://ip-api.com/docs/legal
* Privacy Policy: https://ip-api.com/docs/legal
* The endpoint can be replaced with the cybersec_geo_endpoint filter.

🖥️ Server IP Detection
* Service: https://www.ipify.org/
* Purpose: Detects the server’s public IP address when it cannot be resolved from SERVER_ADDR or DNS
* Data sent: None (the service only returns the caller’s IP)
* When: On demand, at most once per 24 hours (result cached); not on every request

☁️ Cloudflare IP Ranges
* Service: cloudflare.com (public IP list: https://www.cloudflare.com/ips-v4/ and /ips-v6/)
* Purpose: Verifies that a request really comes from Cloudflare before trusting CF-Connecting-IP
* Data sent: None (downloads a public list)
* When: When the Cloudflare header is present, cached for one day; a bundled fallback is used if the download fails

🔄 WordPress.org API
* Service: api.wordpress.org
* Purpose: Checks for WordPress core updates (security score feature)
* Data sent: None (standard WordPress update check)
* When: When the security score is calculated in the admin area
* Privacy Policy: https://wordpress.org/about/privacy/

Quellcode

Der ursprüngliche, nicht minifizierte Entwickler-Quellcode ist im Plugin-Paket (im .zip-Archiv) oder über das SVN-Repository von WordPress.org verfügbar.

Screenshots

Installation

  1. Gehe im WordPress-Adminbereich zu Plugins Plugin hinzufügen
  2. Suche nach „CyberPulse“
  3. Klicke auf Jetzt installieren und dann auf Aktivieren
  4. Navigiere im Admin-Menü zu CyberPulse
  5. ✅ Deine Website ist geschützt — die Standardeinstellungen bieten optimale Sicherheit

FAQ

🔍 Was ist CyberPulse?

CyberPulse (auch als Cyber Pulse geschrieben) ist eine leistungsstarke Sicherheitsfirewall für WordPress, die deine Website in Echtzeit vor Bots, Scannern und Brute-Force-Angriffen schützt.

🌍 Wie funktioniert die IP-Blockierung?

CyberPulse analyses every request locally against its own detection rules and blocks suspicious IPs or entire /24 subnets. You can also manually block IPs, subnets (CIDR), and whitelist trusted IP addresses.

🔍 Wie funktioniert die Bot-Erkennung?

CyberPulse analysiert über 20 Parameter jeder Anfrage: User-Agent, HTTP-Header, Accept-Language, Referer, Browser-Header (Sec-Fetch-*), Verhaltensmuster und mehr. Verdächtige Anfragen werden automatisch durch vorübergehende oder dauerhafte IP-Sperren blockiert.

⚡ Verlangsamt es meine Website?

No. CyberPulse is designed to be lightweight. All checks use efficient caching, and logs are stored in files; the database keeps only settings and small counters. It works smoothly with high-traffic sites.

🔗 Ist es mit Caching- und CDN-Diensten kompatibel?

Ja. Cyber Pulse funktioniert mit WP Rocket, W3 Total Cache, LiteSpeed Cache, Cloudflare und anderen CDN- und Caching-Lösungen. Echte Besucher-IPs werden über Proxy-Header korrekt erkannt.

🔎 Blockiert es Suchmaschinen?

No. Google, Bing, Yandex, Baidu, DuckDuckGo, and other legitimate search bots are automatically detected and whitelisted by IP subnet and User-Agent signature.

✅ Can I whitelist my IP or specific services?

Ja. Du kannst IPs, Subnetze (CIDR), Hostnamen, User-Agent-Muster und bestimmte URL-Pfade auf die Freigabeliste setzen. Administratoren werden bei der Anmeldung automatisch zur Freigabeliste hinzugefügt.

🔐 Wie funktioniert der Brute-Force-Schutz?

When failed login attempts exceed the limit (default: 5 attempts in 15 minutes), the IP gets a temporary block; if 3 or more addresses of the same /24 submit credentials, the whole subnet is banned permanently.

🤖 Schützt es vor KI-Scraping?

Yes. Cyber Pulse blocks known AI training bots: GPTBot (OpenAI), ClaudeBot (Anthropic), PerplexityBot, CCBot (Common Crawl), and others. AI scrapers are detected by User-Agent and IP signatures. For maximum performance, you can optionally enable .htaccess protection to block them before PHP even loads.

⭐ Wodurch unterscheidet sich dies von anderen Sicherheits-Plugins?

CyberPulse offers AI scraping protection, 10 languages out of the box, a real-time dashboard with hourly attack histogram, and a clean interface without third-party ads. It’s lightweight and stores logs in files — not in your database.

🛡️ Gibt es eine PRO-Version?

Ja. PRO fügt Zwei-Faktor-Authentifizierung, Geoblocking (195 Länder), DDoS-Schutz, Malware-Scanner, Kopierschutz für Inhalte, Dateiintegritätsüberwachung und vieles mehr hinzu. Mehr erfahren

Rezensionen

9. Oktober 2026
I've been running CyberPulse on several WordPress sites for a few months now, and it does exactly what it promises — quietly blocks bad traffic in the background without interfering with real visitors or search engines. What I like most: Lightweight and fast. No noticeable impact on page load. Logs are stored in files, not in the database, so it doesn't bloat wp_options like some other security plugins do. Real-time bot blocking. It catches AI scrapers, headless browsers, vulnerability scanners, and brute force attempts automatically. I can see everything in the dashboard. Sane defaults. After installation you get solid protection right away — no need to tweak 50 settings to make it useful. Search engines are whitelisted correctly. Googlebot, Bingbot, Yandex, Baidu, DuckDuckGo, Applebot — none of them get blocked. This is a common problem with other firewalls, so it's a big plus. Support is responsive. I reported a few edge cases and got a fix within days. Clean interface with a dark/light theme, no annoying ads or upsells in the admin panel. Setup took me less than a minute. It works well alongside caching plugins and Cloudflare. The security score dashboard with hourly attack histogram is a nice touch for understanding what's actually hitting the site. Highly recommended if you want real protection without the bloat.
Alle 0 Rezensionen lesen

Mitwirkende und Entwickler

„CyberPulse — Erweiterte Sicherheit und Schutz vor Bots“ ist Open-Source-Software. Folgende Menschen haben an diesem Plugin mitgewirkt:

Mitwirkende

„CyberPulse — Erweiterte Sicherheit und Schutz vor Bots“ wurde in 7 Sprachen übersetzt. Danke an die Übersetzer für ihre Mitwirkung.

Übersetze „CyberPulse — Erweiterte Sicherheit und Schutz vor Bots“ in deine Sprache.

Interessiert an der Entwicklung?

Durchstöbere den Code, sieh dir das SVN-Repository an oder abonniere das Entwicklungsprotokoll per RSS.

Änderungsprotokoll

5.9.1.8

🛡️ Content-Security-Policy headers added. The browser is now told which sources it may load scripts, styles, frames and connections from, so injected code cannot pull in a resource from an attacker’s host. X-Frame-Options ships with it. Off by default, and deliberately permissive for HTTPS sources so CDNs and embedded players keep working.

5.9.1.7

  • 🗄️ Temporary blocks now live in a dedicated database table instead of one option row. Every block is its own row, so two simultaneous blocks can no longer overwrite each other — previously the loser’s block simply disappeared. The upgrade copies the existing blocks into the table on the first admin visit; the option keeps being written as a mirror, so a rollback to an older build still finds every block, and if the table cannot be created the plugin falls back to the option and behaves exactly as before.
  • ⚡ Temporary blocks: the expired-block cleanup now takes the write mutex before reading the list. Previously it scanned first and locked only the write, so a block created in between was overwritten by the stale snapshot.
  • 🧹 Cleanup: removed eleven unused helper functions left over from earlier releases (old diagnostics, the pre-proof-of-work unblock-token generator, an unused UA-stats rebuilder). No behaviour change.

5.9.1.6

  • ⚡ Faster sync: new or lifted temporary blocks mark the edge list as stale and schedule a sync within 30–60 seconds instead of waiting for the five-minute maintenance run.
  • 🚀 Lightweight blocks: HEAD requests, empty User-Agents and command-line scanners (curl, wget, python-requests, sqlmap, nmap, etc.) receive a plain 403 Forbidden under 1 KB instead of the full branded block page.
  • ⚡ Rate limits: the absolute flood threshold is now 100 requests / 10 minutes, and datacenter addresses are limited to 30 / 10 minutes. Verified search engines, whitelisted addresses, administrators and the server itself stay exempt.

5.9.1.5

  • 🔒 Security: Fake bots can no longer slip through. A crawler name in the User-Agent is no longer a free pass — known crawlers must come from their own domains and network (ASN), and spoofed search engines are rejected.
  • 🔒 Security: Login page, XML-RPC, admin pages, and the REST API are now checked early. Previously the main protection layer never saw these requests.
  • 🛡️ Data safety: Background code can no longer wipe permanent bans. Any automatic cleanup that would remove more than 25 records is refused and written to the audit log. Only an administrator can remove bans in bulk.
  • ⚡ Speed: Obvious bots no longer pay for a full WordPress load — cheap checks run first.
  • ⚡ Speed: Rate limits, flood counters, and log deduplication moved to a fast cache layer, so a busy site stops writing to the database on every page view.
  • ⚡ Speed: Heavy admin files load only where they are needed, and dashboard counters are cached.
  • 🎨 Interface: Unban and delete actions work without reloading the page — the row disappears, scroll position is kept, and results are announced politely instead of blocking alerts. Everything still works without JavaScript.
  • 🎨 Interface: The Permaban tile updates instantly after an unban and shows a real breakdown of single addresses and ranges.
  • ⚡ Rate limiting: the effective default is 20 requests per minute. Builds that stored the old 40 value are migrated to 20, because the duplicate check that used to halve it has been removed.

5.9.1.4

  • 🎨 Major UI Overhaul: Completely redesigned the plugin interface to match the premium „CyberPulse“ branding. Enjoy a refreshed dark theme and a fully reworked light theme with a refined color palette, polished grid backgrounds, smoother transitions, and improved overall visual stability.
  • 🔒 Security: Prevented spoofed search engine User-Agents (e.g., fake Googlebot) from accessing sensitive files like .env, config.yml, or wp-config.php.bak. Hidden file pattern checks now run before the search bot whitelist.
  • 🎨 Visual Log Analysis: Tracked page logs are now highly informative. IPs are highlighted in yellow, URLs in green, and Referers in blue for instant visual parsing.
  • 🤖 Bot Detection: Added 9 Joomla/Drupal scanner signatures (/administrator/components/com_*, /plugins/editors/*, /sites/default/*, /templates/system/*, /modules/mod_*, etc.) to the hidden-file scanner. Joomla-targeting bots that hit 404s on WordPress sites are now blocked at first request instead of being counted toward the 404 threshold.
  • ⚡ Reliability: Geo-location lookups now use a 5-second timeout (was 2s), so the geo-location service can respond under load without being incorrectly marked as down.
  • 🐛 Fixed: Legit bot cache is now keyed by IP + User-Agent instead of just IP. This prevents a malicious scanner from inheriting whitelist status if it uses the same IP as a legitimate crawler.
  • 🐛 Fixed: Flood attack auto-permaban now reliably triggers even if the repeat offender counter fails to increment due to DB race conditions. IPs exceeding the rate limit by 5+ requests are now instantly escalated to a permanent subnet ban.

5.9.1.3

  • ⚡ Performance: Lowered the default Rate Limiting threshold from 60 to 40 requests per minute. Added a smart collapsible guide in the UI to help users choose the right value (with CGNAT and mobile carrier warnings).
  • 🛡️ Custom Static 403 Page: When .htaccess protection blocks a bot, it now displays a beautifully styled cyberpulse-403.html page instead of the hosting provider’s default error page.
  • 🔧 Better UX: Replaced the „Back to Home“ button with a „Refresh Page“ button on the static block page, which is more useful for temporary blocks.
  • 🔒 New Free Feature: Force HTTPS 301 redirect with proxy-loop protection, full-width UI, and translations for all 10 supported languages.

5.9.1.2

  • 🤖 AI bot protection is now configurable. Added two independent toggles so you control exactly what gets blocked.
  • 🧠 AI Training Bots (default ON) — blocks GPTBot, CCBot, Google-Extended, ClaudeBot, Bytespider, Amazonbot, etc. They only download your content and never show your site to users.
  • 🔍 AI Search Bots (default OFF) — blocks OAI-SearchBot, ChatGPT-User, PerplexityBot, Claude-User, Amzn-SearchBot, etc. They index your site for AI search engines. Enable this if you want the old strict behavior.
  • 🆕 Expanded signature database — added new AI bots: DuckAssistBot (DuckDuckGo), Amzn-User (Amazon), Grok-DeepSearch (xAI), QwenBot (Alibaba), DeepSeekBot, xAI-Crawler, and cohere-training-data-crawler.
  • 🛡️ New server-aware .htaccess panel: shows „Recommended: ON“ on Apache/LiteSpeed with a writable file, warns clearly on nginx or read-only setups, and disables the checkbox when the feature cannot work.

5.9.1.1

  • 🔒 Security: User-Agent validation rewritten — hardcoded Chrome version threshold replaced with behavioural verification (Sec-Fetch-*, Client Hints, Accept-Language).
  • 🤖 Bot Detection: Added WebView whitelist (Instagram, Facebook, TikTok, Telegram, Snapchat, Pinterest, LinkedIn, WeChat, LINE, KakaoTalk, Viber, Twitter) to prevent false positives on mobile in-app browsers.
  • ⚡ Reliability: Temporary blocks now survive alloptions cache invalidation — fixes rare cases where a blocked IP was allowed again within seconds.

5.9.1.0

  • 🔒 Security: AI scraper check now runs first, before the human-test window. Bots that pass the captcha once are still checked against AI signatures on every subsequent request. Admin IPs remain exempt.
  • 🔒 Security: Request flood protection now issues temporary blocks for heuristic evidence (traffic spike, datacenter IP) and reserves permanent subnet bans for repeat offenders only — reduces false positives without weakening the protection.
  • 🔒 Reliability: Server IP is now re-validated every 24 hours instead of being cached indefinitely. A hosting migration or proxy change is picked up automatically, and private/reserved addresses from reverse-proxy setups are rejected at every step.
  • ⚡ Performance: Radically optimized admin panel loading by eliminating blocking GeoIP requests, implementing smart log reading (200KB) with a 1000-row display limit to prevent UI freezing (full files are still processed during download/copy).
  • ⚡ Performance: Log writes are now ~50× faster on busy sites, with ~5× lower memory use during rotation. Leftover .log.1 files from older versions are cleaned up automatically.

5.9.0.9

  • 🔒 Security & Feature: .htaccess protection is now opt-in (disabled by default) and managed via a new „AI Scraping Protection“ settings block. The ruleset was also extended to block .git, .env, .sql dumps, and other sensitive files before PHP loads.
  • 🤖 Bot Detection: Unified and expanded detection logic — added 12 new AI bot signatures (Claude-User, xAI-Grok, etc.) and implemented Mac+Chrome antidetect checks to catch residential proxy bot farms. Also blocked fake GPTBot/ClaudeBot impersonation and scrapers masquerading as mobile apps (TikTokSpider, InstagramScraper).
  • 🎨 UI: Brute Force panel now displays the full history of login attempts (active and inactive) with clear limit indicators.

5.9.0.8

  • 🚀 Major Performance Boost: Complete dashboard overhaul — log files are now read only once, and CSS rendering optimizations allow you to smoothly view thousands of log rows without any lag.
  • ⚡ Backend Optimization: Restored object caching for threat levels, top offenders, and UA statistics. Rate limiting is now working properly, and background tasks are safely throttled.
  • 🎨 Interactive Dashboard: All cards (KPI and Pulse) are now clickable with smooth-scroll navigation to relevant sections. Added informative tooltips and replaced confusing percentages with clear numerical differences.

5.9.0.7

  • 🔒 Search engine protection: Google, Yandex, Bing, Baidu, Apple, Meta, Telegram, Twitter, and Cloudflare subnets bypass permaban
  • 🔒 Automated cleanup of search engine subnets from permanent block list
  • 🔒 Instant-pass whitelist for verified search bots
  • 🔒 Fake-UA guard: search bots with „Chrome/“ in User-Agent fall back to regular checks
  • 🔒 Subnet size guard: permaban skips subnets wider than /16 (IPv4) or /32 (IPv6)
  • ⚡ Rate limiting and 404 detection skip verified search engine bots
  • ⚡ Performance: merged whitelist checks into a single compact sanity check
  • ✅ New helpers: cybersec_is_search_engine_subnet(), cybersec_purge_search_engine_subnets_from_permaban()
  • 🎨 Complete UI redesign — cleaner, more professional interface across all admin tabs
  • 🎨 New light theme „CyberPulse Daylight“ — warm green palette, brand grid pattern, saturated accent, chunky shadows

5.9.0.6

  • 🔒 Security: Fixed brute force protection bypass via _wpnonce parameter
  • 🔒 Security: Fixed privilege escalation via whitelist note field — admin IPs now use explicit auto_type marker
  • 🐛 Fixed: XSS check on AJAX human verification now reads raw request data
  • 🐛 Fixed: Chrome parsers with fixed old builds now blocked
  • ✅ Added: Extended bot UA blacklist (CVE-validators, unknown crawlers, NetAPI)
  • ⚡ Performance: Cached cybersec_check_ai_scraper() result within single request
  • 🧹 Cleanup: Activated cybersec_sync_page_logs_stats() — page counters now auto-refresh every 5 min

5.9.0.5

  • ✅ Added: Extended whitelist for search engines and monitoring services
  • ✅ Added: Extended Yandex subnet list
  • ✅ Added: Extended SQL injection patterns and audit logging
  • 🔒 Security: Improved bot detection integration

5.9.0.4

  • 🐛 Fixed: 403 block page styles not loading
  • ⚡ Added: pulsing glow animation on 403 page icon

5.9.0.3

  • 🔒 Added: permaban check to hide_wordpress, hide_plugins_themes, rate_limiting, 404_detection, url_firewall
  • 🔒 Added: permaban check to cybersec_check_all before all blocking checks
  • ⚡ Added: static file exclusion in hide_wordpress (CSS, JS, images no longer trigger hide_wp checks)
  • 🔧 Fixed: Server IP retrieval (cybersec_get_server_ip) — proper wp_unslash + sanitize
  • 🐛 Fixed: Duplicate logging — added dedup window in cybersec_log_blocked_bot
  • 🐛 Fixed: Scanner logging spam — added deduplication for repeated identical log entries

5.9.0.2

  • ⚡ Performance: Optimized cybersec_is_real_browser() — reduced from 120+ stripos() calls to 3-4 preg_match() operations (95% faster)
  • ⚡ Performance: Optimized cybersec_is_legitimate_bot() — reduced from 60+ operations to 5-10 (85% faster)
  • 🚀 Added PTR (reverse DNS) verification for legitimate bots (Googlebot, Bingbot, Yandex, etc.)
  • 🔒 Security: Added permanent block for system file access attempts (wp-config.php, .env, .git, etc.)

5.9.0.1

  • 🔧 Fixed: Counter mismatch between statistics and log files (hotfix)
  • 🔧 Fixed: Statistics cache causing stale data (removed cache)
  • 🔧 Fixed: Duplicate entries in blocked/allowed logs (60-second dedup)
  • 🔧 Fixed: Tracked pages showing nested subpages (exact match only)
  • 🔧 Fixed: Internal/private IPs shown in logs

5.9.0.0

  • 🔧 Fixed: Counter mismatch between statistics and log files
  • 🔧 Fixed: Statistics cache causing stale data (removed cache, count directly from files)
  • 🔧 Fixed: Duplicate entries in blocked/allowed logs
  • 🔧 Fixed: Internal/private IPs shown in logs (10.x.x.x, 172.16.x.x, 192.168.x.x, 100.64.x.x)
  • ⚡ Improved: Dashboard order (Security Score Allowed Blocked Page Tracking Event Log)
  • ⚡ Improved: Direct file counting for accurate statistics

5.8.9.9

  • 🔒 Security: Fixed XSS vulnerabilities in 403 block page (replaced esc_url with esc_js for JavaScript context)
  • 🔒 Security: Added strip_tags() before htmlspecialchars() in XSS detection to prevent stored XSS attacks
  • 🔒 Security: Fixed SQL injection vulnerability in stale transients cleanup query
  • 🔒 Security: Added current_user_can(‚manage_options‘) check to cybersec_handle_simple_check()
  • 🔒 Security: Added IP validation in cybersec_ajax_human_verify() AJAX handler
  • 🔒 Security: Added sanitize_text_field() for User-Agent in track_user_agent() function
  • 🔒 Security: Fixed cookie removal logic in cybersec_remove_all_blocks()
  • ⚡ Performance: Added throttling to cybersec_cleanup_expired_temp_blocks() (5 min cooldown)
  • 🔧 Fixed: Proper variable naming in cybersec_cleanup_stale_transients() foreach loop
  • 🐛 Fixed: Potential memory issue in cybersec_fs_put_contents() with large log files

5.8.9.8

  • 🔒 Security fix: Added XSS protection with input sanitization and esc_url_raw
  • 🛡️ Fixed 403 page bugs: increased token lifetime, IP validation
  • 🚀 Performance optimization: added wp_cache for settings and whitelist
  • 🔧 Fixed cron schedule error: registered cyberpulse_every_5_minutes
  • 🧹 Added directory traversal protection in log functions
  • ✅ Added nonce verification in AJAX human-verify handler
  • 🔄 Full data cleanup on IP unblock (cookies, cache, transients)

5.8.9.7

  • 🚀 Performance optimization: Added Object Cache support for 15+ functions (whitelist, offenders, threat level, UA stats, and more)
  • 🛡️ Security enhancement: Removed browser header bypass in request checks, improved XSS validation for all users
  • ⚡ Improved bot detection: Expanded real browser detection with 50+ UA patterns (VK, Telegram, WhatsApp, Instagram, and more)
  • 🔧 Optimized log rotation with safe truncation to prevent file corruption
  • 🧹 Enhanced transient cleanup with lower DB load
  • 🌐 Added caching for geo-location lookups
  • 📈 Security test now validates 20+ protection features

5.8.9

  • 🌍 Übersetzungsdateien für 10 Sprachen hinzugefügt
  • 🔗 Link zur PRO-Website aktualisiert
  • 🛠️ SQL-Kompatibilität mit MariaDB behoben

5.8.6

  • 🚀 Erstveröffentlichung mit KI-Scraping-Schutz, Bot-Erkennung, Brute-Force-Abwehr und mehr