WordPress Plugin
Comprehensive security hardening, HTTP header management, login protection, request firewall, REST API protection, and security auditing — all from a single, lightweight plugin.
What is Security Pilot?
Security Pilot is a comprehensive WordPress security plugin that hardens your site against common attacks and vulnerabilities. It implements industry-standard HTTP security headers, protects your login page from brute-force attacks, blocks malicious requests with a built-in firewall, and restricts sensitive REST API endpoints.
Unlike bloated security suites, Security Pilot is lightweight and modular — enable only the protections you need. Every security module can be individually toggled, and all settings are managed from a single, clean admin page.
Key Benefits:
- HTTP security headers (HSTS, CSP, X-Frame-Options, and more)
- Login protection with rate limiting, lockouts, and permanent bans
- Request firewall scanning for SQLi, XSS, path traversal, and command injection
- REST API endpoint protection (users, WooCommerce, Jetpack, Divi, Elementor)
- WordPress hardening (disable file editor, XML-RPC, version exposure)
- Security audit for outdated/inactive plugins and themes
- Attack logging and IP blocking/whitelisting
Key Features
HTTP Security Headers
Automatically set X-Frame-Options, X-Content-Type-Options, X-XSS-Protection, HSTS, Referrer-Policy, Permissions-Policy, and Content-Security-Policy. Remove the X-Powered-By header that reveals your server technology.
Login Protection
Block brute-force attacks with configurable rate limiting. Set max failed attempts, lockout duration, and permanent ban thresholds. Receive email alerts on attacks and IP blocks. Hide detailed error messages.
Request Firewall
Scan incoming requests for SQL injection, cross-site scripting (XSS), path traversal, remote file inclusion (RFI), and command injection patterns. Malicious requests receive a 403 Forbidden response.
REST API Protection
Block unauthorized access to sensitive endpoints: /wp/v2/users (user enumeration), WooCommerce, Jetpack, wp-site-health, Divi Builder, and Elementor endpoints.
WordPress Hardening
Disable the theme/plugin file editor, XML-RPC, pingbacks and trackbacks. Hide WordPress version from HTML source. Remove RSD link and WLW manifest.
Security Audit
Run security checks to identify outdated plugins, outdated themes, and inactive plugins that may pose security risks. Get actionable recommendations.
Admin Interface
Configuration Guide
HTTP Security Headers
Navigate to Settings → Security Pilot.
Toggle individual headers on/off. Each header protects against specific attack vectors:
- X-Frame-Options: SAMEORIGIN — prevents clickjacking
- X-Content-Type-Options: nosniff — prevents MIME-type sniffing
- Strict-Transport-Security (HSTS) — enforces HTTPS connections
- Content-Security-Policy — controls resource loading origins
Login Protection
- Max Failed Attempts: Number of failures before lockout (1–20, default: 5)
- Attempt Window: Time window for counting failures (1–120 minutes)
- Lockout Duration: How long a locked-out IP stays blocked (1–1440 minutes)
- Permanent Ban: Lockouts before permanent ban (1–20)
Email alerts for attacks and IP blocks (configurable).
Request Firewall
Enable the firewall module — it automatically scans all incoming requests.
No configuration needed — detection patterns are built-in and cover SQLi, XSS, path traversal, RFI, and command injection.
REST API Protection
Toggle protection for each endpoint group independently.
Protected groups: /wp/v2/users, WooCommerce, Jetpack, wp-site-health, Divi Builder, Elementor.
WordPress Hardening
Each hardening option can be enabled independently.
Recommended: Disable file editor, XML-RPC, and version exposure for all production sites.
Getting Started
- Install and activate Security Pilot.
- Navigate to Settings → Security Pilot.
- Enable HTTP Security Headers — start with the recommended defaults.
- Enable Login Protection and configure max failed attempts (5 is a good default).
- Enable the Request Firewall for automatic malicious request blocking.
- Toggle REST API Protection for endpoints you don't need exposed.
- Enable WordPress Hardening options (especially disable file editor on production).
- Run a Security Audit to identify any outdated plugins or themes.
Requirements
- WordPress 5.8+, PHP 7.4+
- No external services or API keys required
Protect Your WordPress Site
Enterprise-grade security hardening without the complexity.
