Description
CoxWall is a powerful and lightweight WordPress security plugin designed to protect your website from modern security threats, brute-force attacks, malware attempts, and unauthorized access.
It provides advanced security tools including firewall protection, login hardening, security headers, file integrity monitoring, WooCommerce security, and detailed audit logging — all in an easy-to-use interface.
Whether you run a blog, business website, membership platform, or WooCommerce store, CoxWall helps keep your WordPress site secure and protected in real time.
Key Features:
- Login Protection – Adaptive rate limiting per IP, per username, per username + IP, and site-wide, with separate limits for XML-RPC and password resets, progressive delays, escalating lockouts, and email alerts.
- Hide Login – Move your login URL away from the default
wp-login.php. - CAPTCHA – Google reCAPTCHA v2 / v3 on login, registration, and WooCommerce forms.
- Firewall – Block SQLi, XSS, directory traversal, malicious bots, and XML-RPC abuse.
- Security Headers – Set X-Frame-Options, CSP, HSTS, Referrer-Policy, and more.
- File Integrity – Detect changes to WordPress core and plugin files.
- WooCommerce – Extra security for WooCommerce stores.
- Audit Log – Full event log with IP, user, and timestamp for every security event.
- Login History – Track successful and failed login attempts with user, IP, browser, device, and login time details.
- Early Blocking – Ready-to-paste Cloudflare, Nginx, and Apache rules for your login and XML-RPC endpoints, so abusive traffic can be refused before it reaches WordPress.
Why Choose CoxWall?
- Lightweight and performance-friendly
- Beginner-friendly setup
- Modern security protection
- WooCommerce compatible
- Advanced firewall system
- Detailed security logging
- Real-time protection and monitoring
CoxWall helps you secure your WordPress website with enterprise-level protection while keeping the setup simple and user-friendly.
Features:
- Login Protection
- Hide Login URL
- Google reCAPTCHA v2 / v3
- Firewall Protection
- SQL Injection (SQLi) Blocking
- XSS Attack Protection
- Directory Traversal Protection
- Malicious Bot Blocking
- XML-RPC Protection
- Security Headers Management
- Content Security Policy (CSP)
- HSTS Support
- Referrer Policy Protection
- File Integrity Monitoring
- Core File Change Detection
- Plugin File Change Detection
- WooCommerce Security
- Audit Log System
- IP Activity Logging
- User Activity Tracking
- Real-time Security Alerts
- Email Notifications
- Brute-force Protection
- Login Attempt Limiting
- IP Lockout System
- Malware Defense
- Website Hardening
- Real-time Monitoring
- WordPress Security Suite
External services
This plugin optionally connects to the following third-party / external services. Each service is only contacted when its corresponding module is enabled and the described conditions are met.
Google reCAPTCHA (Google LLC)
What it is and what it is used for:
Google reCAPTCHA is a bot-detection service. CoxWall uses it to protect the WordPress login, registration, lost-password, comment, and WooCommerce My Account forms from automated attacks.
What data is sent and when:
When the CAPTCHA module is enabled, two types of requests are made to Google:
- Front-end (page load) – the visitor’s browser loads the reCAPTCHA JavaScript library directly from Google’s CDN (
www.google.com). Google receives the visitor’s IP address, browser and device information, and the site’s public reCAPTCHA site key. - Back-end (form submission) – when a visitor submits a protected form, the plugin sends the reCAPTCHA response token, the site’s secret key, and the visitor’s IP address to Google’s verification endpoint (
www.google.com/recaptcha/api/siteverify) to confirm the response is valid.
No data is sent if the CAPTCHA module is disabled or if no reCAPTCHA site/secret key has been configured.
Service provider links:
* Terms of Service: https://policies.google.com/terms
* Privacy Policy: https://policies.google.com/privacy
* reCAPTCHA-specific information: https://developers.google.com/recaptcha
WordPress.org Core Checksums API (WordPress.org)
What it is and what it is used for:
The WordPress.org Checksums API provides official MD5 hashes for every file in each WordPress core release. CoxWall’s File Integrity module uses these hashes to detect unauthorized modifications to core files.
What data is sent and when:
When a file integrity scan runs (manually triggered or on schedule), the plugin sends a GET request to https://api.wordpress.org/core/checksums/1.0/ containing:
- The installed WordPress version number.
- The site’s configured locale/language.
No personal data, user data, or site content is transmitted. The request retrieves a publicly available checksum list.
Service provider links:
* Privacy Policy: https://wordpress.org/about/privacy/
* API documentation: https://codex.wordpress.org/WordPress.org_API
Privacy Policy
CoxWall uses Appsero SDK to collect some telemetry data upon user’s confirmation. This helps us to troubleshoot problems faster & make product improvements.
Appsero SDK does not gather any data by default. The SDK only starts gathering basic telemetry data when a user allows it via the admin notice. We collect the data to ensure a great user experience for all our users.
Integrating Appsero SDK DOES NOT IMMEDIATELY start gathering data, without confirmation from users in any case.
Learn more about how Appsero collects and uses this data.
Installation
- Upload the
coxwallfolder to/wp-content/plugins/. - Activate the plugin through the Plugins menu in WordPress.
- Navigate to CoxWall → Dashboard to configure.
FAQ
Does CoxWall block attacks before WordPress or PHP runs?
No. CoxWall is a WordPress plugin, so it runs inside WordPress: every request it blocks has already reached your server and started PHP. It stops the attack, but the server still does some work for each request.
To refuse abusive traffic earlier, go to CoxWall → Early Blocking. It generates rules for this site’s login and XML-RPC addresses that you (or your host) add to Cloudflare, Nginx, or Apache. Those rules act before PHP starts. CoxWall does not edit server configuration files or your Cloudflare account; you apply the rules yourself. Keep CoxWall enabled as a second layer behind them.
My site is behind Cloudflare or a load balancer. What do I need to set?
Go to CoxWall → Early Blocking → Cloudflare → Visitor IP Detection and turn on Behind Cloudflare, or list your load balancer’s IPs under Trusted Proxies. Otherwise every visitor appears to come from the proxy’s IP, and login lockouts or IP blocks would affect everyone.
Screenshots
Changelog
Unreleased
- Added: Early Blocking page with Cloudflare WAF / rate-limiting rules and Nginx / Apache snippets for the login and XML-RPC endpoints, generated for each site’s paths and settings.
- Added: Visitor IP Detection settings (Behind Cloudflare, Trusted Proxies). Forwarded-IP headers are now only trusted from trusted proxies.
- Added: Adaptive login rate limiting — separate limits per IP, per username (including nonexistent ones), per username + IP, site-wide, for XML-RPC authentication, and for password-reset requests; each with its own time window.
- Added: Progressive delays between failed logins, escalating lockouts for repeat offenders, temporary bans, and an Active Lockouts list where admins can clear lockouts.
- Added: Optional email activation for new self-registered accounts (WordPress and WooCommerce) — users must click an emailed link before they can log in, with expiring links, automatic resend on login, and activate/resend actions on the Users screen.
- Added: reCAPTCHA option for the WooCommerce My Account registration form.
- Added: Registration email validation for WordPress, multisite, and WooCommerce (My Account and checkout) — blocks test/example addresses, placeholder names, disposable inbox services, custom blocked domains, and domains without a mail server; optional “known providers only” mode.
- Added: User role column in Login History.
- Added: Bulk clearing of the Event Log — delete selected rows, or clear by event type and age. Each clear is itself recorded in the log.
- Added: PHP Version card on the Dashboard.
- Added: Bulk deletion in Login History — delete selected records, or clear by status and age. Each clear is recorded in the Event Log.
- Fixed: Login Limit lockout could be bypassed with a correct password on WooCommerce and XML-RPC logins when the Firewall module was disabled.
- Security: Firewall no longer blocks ordinary text (searches, comments, forms containing words like “update” or “select”); SQL injection rules now require real SQL syntax; administrators and editors are exempt from payload inspection; a single match blocks only that request and IPs are banned only after repeated hits — never for requests triggered by another website.
- Security: Firewall now inspects nested parameters and parameter names.
- Security: Login CAPTCHA could be skipped by omitting the form’s submit-button field.
- Security: Checkout CAPTCHA now also protects the WooCommerce block checkout (Store API).
- Security: reCAPTCHA responses are now checked for this site’s hostname and, for v3, the expected action.
- Security: Hide Login no longer reveals the custom login URL via /wp-admin/ or the /login, /admin and /dashboard shortcuts.
- Security: Login History stores session tokens hashed instead of in plain text (existing records are converted on upgrade).
- Fixed: An invalid CIDR range (e.g. /33) in an IP list could crash every page; IP lists are now validated on save.
- Fixed: The comment-form CAPTCHA error message never appeared, and it no longer takes its text from the URL.
- Fixed: Missing usage-tracking library no longer causes a fatal error.
1.0.2
- Added: Early Blocking system
- Added: Contact Form 7 forms
- Added: WooCommerce My Account register form
- Added: Login History delete option
- Added: user role show option in Login History table
1.0.1
- Added: Login History — tracks username, login date/time, logout date/time, IP address, device, browser, operating system, login status, session duration, last activity, and referrer for every login attempt.
- Added: Filter Login History by username, user role, success/failed status, date range, IP address, browser, operating system, device, and login method.
- Added: Terminate an active session directly from the Login History screen.
- Added: Configurable retention period for Login History records, with automatic daily cleanup.
1.0.0
- Initial release.




