=== Atomic Edge Security - Firewall, Malware Scan and Login Security === Contributors: shift8 Tags: 2FA, Firewall, Malware, Scanner, Security Requires at least: 5.8 Tested up to: 6.9 Requires PHP: 7.4 Stable tag: 2.5.6 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html WordPress firewall with cloud WAF rules, malware scanning, 2FA, vulnerability checks, IP blocking, and real-time security logs. == Description == Atomic Edge Security is a WordPress firewall plugin that protects your site with cloud-based WAF rules, malware scanning, 2FA, vulnerability checks, IP blocking, and real-time security logs. It blocks malicious traffic before it reaches WordPress while giving site owners firewall controls directly inside the WordPress admin. [youtube https://www.youtube.com/watch?v=HP_EiWLtuZE] = WordPress Firewall Protection = Atomic Edge includes a cloud-based WordPress firewall that helps block malicious traffic before it reaches your website. The firewall protects against common attacks such as SQL injection, cross-site scripting (XSS), local file inclusion, remote file inclusion, brute-force login attempts, and suspicious bot activity. = Web Application Firewall (WAF) = The Atomic Edge WAF uses OWASP Core Rules and WordPress-specific security rules to protect high-risk areas such as wp-login.php, wp-admin, XML-RPC, REST API endpoints, vulnerable plugin paths, and common exploit patterns. = Features = * **Two-Factor Authentication (2FA)** - Protect WordPress logins with TOTP authenticator apps (Google Authenticator, Authy, etc.) * **2FA Enforcement Policies** - Require 2FA for specific user roles with configurable grace periods * **2FA Audit Logging** - Complete security audit trail for all 2FA events * **Adaptive Defense** - AI-powered threat detection that automatically identifies and blocks malicious actors * **Web Application Firewall (WAF)** - Block SQL injection, XSS, and other attacks with OWASP Core Rules * **Content Delivery Network (CDN)** - Serve static assets from global edge servers for faster page loads * **Real-time Analytics** - Monitor traffic, blocked threats, and security events in real-time * **IP Access Control** - Easily whitelist or blacklist IP addresses and CIDR ranges * **Geographic Blocking** - Block or allow access based on visitor country * **Malware Scanner** - Scan WordPress files for modifications and suspicious code patterns * **Vulnerability Scanner** - Check WordPress core, plugins, and themes for known vulnerabilities (requires Atomic Edge connection) * **WAF Log Viewer** - See exactly what threats are being blocked * **WP-CLI Integration** - Run security scans from the command line = How It Works = 1. Sign up for an Atomic Edge account at [atomicedge.io](https://atomicedge.io) 2. Add your site to Atomic Edge and get your API key 3. Install this plugin and enter your API key 4. Manage your security settings directly from WordPress Vulnerability scanning is available when connected and uses Atomic Edge's vulnerability data feed. = Requirements = * PHP 7.4 or higher * WordPress 5.8 or higher * An Atomic Edge account (free tier available) * OpenSSL PHP extension == Installation == 1. Upload the `atomic-edge-security` folder to the `/wp-content/plugins/` directory 2. Activate the plugin through the 'Plugins' menu in WordPress 3. Go to Atomic Edge > Settings and enter your API key 4. Your site is now protected! == Frequently Asked Questions == = Do I need an Atomic Edge account? = Yes, this plugin requires an Atomic Edge account to function. You can sign up for free at [atomicedge.io](https://atomicedge.io). = Is there a free tier? = Yes! Atomic Edge offers a free tier with basic WAF protection. Advanced features are available on paid plans. = How do I get my API key? = After creating your Atomic Edge account and adding your site, you can generate an API key from the site settings page in your Atomic Edge dashboard. = Does this plugin slow down my site? = No. The Atomic Edge WAF runs on our edge servers, not on your WordPress installation. The plugin only communicates with our API for configuration and analytics. = Does the plugin include vulnerability scanning? = Yes. When your site is connected to Atomic Edge, you can run a vulnerability scan of WordPress core, plugins, and themes from the Atomic Edge admin menu. = What attacks does the WAF block? = Atomic Edge uses the OWASP Core Rule Set to block: * SQL Injection * Cross-Site Scripting (XSS) * Remote File Inclusion * Local File Inclusion * And many more common attack vectors = Does Two-Factor Authentication (2FA) work without an Atomic Edge account? = Yes! The 2FA feature works independently and does not require an Atomic Edge account or API connection. It uses industry-standard TOTP (Time-based One-Time Password) compatible with Google Authenticator, Authy, 1Password, and other authenticator apps. = What are the server requirements for 2FA? = 2FA requires PHP 7.2+ with either: * Native libsodium extension (recommended, included in most modern PHP installations), OR * WordPress 5.2+ (which includes sodium_compat, a pure PHP fallback) The plugin automatically detects and uses the best available option. == Screenshots == 1. Dashboard summary showing connection status, security overview, and quick actions 2. Analytics page with traffic graphs and data for requests and blocked threats 3. WAF log viewer displaying security incidents and blocked attacks in real-time 4. Access control management for IP whitelist, blacklist, and geographic blocking 5. Malware scanner to scan your entire WordPress installation for malicious files 6. Vulnerability scanner highlighting insecure or vulnerable core, themes, and plugins 7. CDN settings page for configuring content delivery and asset optimization 8. Two-Factor Authentication settings for securing WordPress login with TOTP apps 9. Adaptive Defense dashboard showing AI-powered threat detections and automatic IP blocking == Changelog == = 2.5.6 = * CHANGE: Updated WordPress.org directory title, tags, and short description for better discoverability = 2.5.4 = * FIX: Minification persisted after being disabled — stale cached files were not cleared on toggle off * FIX: Clear minification cache button silently failed — wp_delete_file() return value was incorrectly checked * FIX: Cache clear now verifies file deletion with file_exists() and reports accurate deleted count * CHANGE: Disabling CSS or JS minification now auto-clears the minification cache * CLEANUP: Removed dead AJAX handler with mismatched nonce in CDN class = 2.5.3 = * FIX: Removed hardcoded malware signature strings from scanner that triggered ClamAV false-positive (Txt.Backdoor.Webshell-9891631-0) on hosting providers * CHANGE: Refined plugin patterns now sourced exclusively from API instead of local hardcoded strings = 2.5.2 = * FIX: CDN toggle not persisting after save — hourly cron sync was overwriting CDN data instead of merging * FIX: Saving CDN settings from Minification or Advanced tabs incorrectly disabled CDN * FIX: Removed debug logging from CDN settings save handler = 2.5.1 = * CHANGE: WAF Logs "Block IP" button renamed to "Blacklist" — now adds IPs to edge-level IP Blacklist instead of Adaptive Defense * NEW: Dev mode support for WAF logs blacklist button * NEW: AJAX nonce auto-refresh — expired nonces are transparently refreshed without page reload = 2.5.0 = * NEW: Vulnerability scanner now works without an API key — free scans limited to 3 per day per IP * NEW: Rate limit exceeded warning displayed in dashboard when daily scan limit is reached * CHANGE: Vulnerability scanner availability no longer gated on API connection status = 2.4.8 = * NEW: Added Blocked IPs tab to Adaptive Defense with IP Address, Threat Score, WAF Hits, Type, Blocked, Expires columns and actions (Extend, Make Permanent, Unblock) * FIX: Adaptive Defense block actions now route through dashboard Blocked IPs (application-layer) instead of Access Control IP blacklist (edge config) * NEW: Manual block form on Blocked IPs tab with configurable duration (1h, 6h, 24h, 7d, 30d, permanent) * NEW: Extend block (+1 day) and Make Permanent actions for timed blocks * CHANGE: WAF Logs "Block IP" button renamed to "Blacklist IP" to clarify it adds to edge-level IP blacklist * NEW: Added extend_block() and make_permanent() API methods and AJAX handlers with dev mode support = 2.4.7 = * FIX: Confidence now displayed as percentage (e.g. "90%") instead of raw decimal ("0.90%") in Adaptive Defense threat detection details * FIX: Dev mode simulation data now uses 0.0-1.0 decimal values for confidence to match real API format = 2.4.6 = * FIX: Adaptive Defense dev mode now provides simulated data for all 8 AJAX endpoints (overview, actor profiles, threat detections, detection detail, block/unblock IP, dismiss detection, delete actor) * FIX: Fixed duplicate detail rows appending on repeated "View Details" clicks in Threat Detections tab by replacing invalid
-wrapped template with HTML5