themelooks

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:
<ul>
<li>Login Protection – Limit login attempts per IP, lock out attackers, and receive email alerts.</li>
<li>Hide Login – Move your login URL away from the default <code>wp-login.php</code>.</li>
<li>CAPTCHA – Google reCAPTCHA v2 / v3 on login, registration, and WooCommerce forms.</li>
<li>Firewall – Block SQLi, XSS, directory traversal, malicious bots, and XML-RPC abuse.</li>
<li>Security Headers – Set X-Frame-Options, CSP, HSTS, Referrer-Policy, and more.</li>
<li>File Integrity – Detect changes to WordPress core and plugin files.</li>
<li>WooCommerce – Extra security for WooCommerce stores.</li>
<li>Audit Log – Full event log with IP, user, and timestamp for every security event.</li>
</ul>
Why Choose CoxWall?
<ul>
<li>Lightweight and performance-friendly</li>
<li>Beginner-friendly setup</li>
<li>Modern security protection</li>
<li>WooCommerce compatible</li>
<li>Advanced firewall system</li>
<li>Detailed security logging</li>
<li>Real-time protection and monitoring</li>
</ul>
CoxWall helps you secure your WordPress website with enterprise-level protection while keeping the setup simple and user-friendly.
Features:
<ul>
<li>Login Protection</li>
<li>Hide Login URL</li>
<li>Google reCAPTCHA v2 / v3</li>
<li>Firewall Protection</li>
<li>SQL Injection (SQLi) Blocking</li>
<li>XSS Attack Protection</li>
<li>Directory Traversal Protection</li>
<li>Malicious Bot Blocking</li>
<li>XML-RPC Protection</li>
<li>Security Headers Management</li>
<li>Content Security Policy (CSP)</li>
<li>HSTS Support</li>
<li>Referrer Policy Protection</li>
<li>File Integrity Monitoring</li>
<li>Core File Change Detection</li>
<li>Plugin File Change Detection</li>
<li>WooCommerce Security</li>
<li>Audit Log System</li>
<li>IP Activity Logging</li>
<li>User Activity Tracking</li>
<li>Real-time Security Alerts</li>
<li>Email Notifications</li>
<li>Brute-force Protection</li>
<li>Login Attempt Limiting</li>
<li>IP Lockout System</li>
<li>Malware Defense</li>
<li>Website Hardening</li>
<li>Real-time Monitoring</li>
<li>WordPress Security Suite</li>
</ul>
<h3>External services</h3>
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.
<h4>Google reCAPTCHA (Google LLC)</h4>
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:
<ol>
<li>Front-end (page load) – the visitor’s browser loads the reCAPTCHA JavaScript library directly from Google’s CDN (<code>www.google.com</code>). Google receives the visitor’s IP address, browser and device information, and the site’s public reCAPTCHA site key.</li>
<li>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 (<code>www.google.com/recaptcha/api/siteverify</code>) to confirm the response is valid.</li>
</ol>
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
<h4>WordPress.org Core Checksums API (WordPress.org)</h4>
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 <code>https://api.wordpress.org/core/checksums/1.0/</code> containing:
<ul>
<li>The installed WordPress version number.</li>
<li>The site’s configured locale/language.</li>
</ul>
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

CoxWall

Professional WordPress security plugin with firewall, brute-force protection, login hardening, security headers, and file integrity monitoring.

Marc Armengou

Security Hardener applies WordPress security best practices based on the <a href="https://developer.wordpress.org/advanced-administration/security/hardening/" rel="nofollow ugc">WordPress Advanced Administration / Security / Hardening</a> documentation and widely accepted hardening measures. It uses WordPress core functions and follows best practices without modifying core files.
<h4>Key Features</h4>
File Security: 
* Disable file editor in WordPress admin 
* Optionally disable all file modifications
XML-RPC Protection: 
* Disable XML-RPC completely 
* Remove pingback methods when XML-RPC is enabled
Pingback Protection: 
* Disable self-pingbacks 
* Remove X-Pingback header 
* Block incoming pingbacks
User Enumeration Protection: 
* Block <code>/?author=N</code> queries (returns 404) 
* Secure REST API user endpoints (require authentication) 
* Remove users from XML sitemaps 
* Prevent canonical redirects that expose usernames 
* Optionally block author feed pages (<code>/author/username/feed/</code>) 
* Optionally anonymize the author name in oEmbed responses
Login Security: 
* Generic error messages (no username/password hints) 
* Login honeypot 
* Block unsafe usernames 
* Application Passwords disabled by default 
* IP-based rate limiting with configurable thresholds 
* Security event logging
Security Headers: 
* <code>X-Frame-Options: SAMEORIGIN</code> (clickjacking protection) 
* <code>X-Content-Type-Options: nosniff</code> (MIME sniffing protection) 
* <code>Referrer-Policy: strict-origin-when-cross-origin</code> 
* <code>Permissions-Policy</code> (restricts geolocation, microphone, camera) 
* Optional HSTS (HTTP Strict Transport Security) for HTTPS sites — max-age set to 1 year
Additional Hardening: 
* Hide WordPress version (meta generator tag and asset query strings) 
* Remove obsolete wp_head items (RSD, WLW manifest, shortlink, emoji scripts) 
* System Status — monitors file permissions, WP_DEBUG, user registration, PHP version, administrator accounts, and database version
<blockquote>
⚠️ Important: Always test security settings in a staging environment first. Some features may affect third-party integrations or plugins.
</blockquote>
Privacy: This plugin does not send data to external services and does not create custom database tables. It stores plugin settings and a security event log in the WordPress options table, and uses transients for temporary login attempt tracking. All data is preserved on uninstall by default and only deleted if the “Delete all data on uninstall” option is explicitly enabled.

Security Hardener

Basic hardening: secure headers, login honeypot, user enumeration blocking, generic login errors, rate limiting, and more.

CoxWall vs Security Hardener