| 1 |
=== Vigilant - 100% Free Security Suite: Firewall, 2FA, Login, Headers, Scanner… === |
| 2 |
Contributors: fernandot, ayudawp |
| 3 |
Tags: security, firewall, 2fa, malware, scanner |
| 4 |
Requires at least: 6.2 |
| 5 |
Tested up to: 7.1 |
| 6 |
Requires PHP: 7.4 |
| 7 |
Stable tag: 2.11.2 |
| 8 |
License: GPL v2 or later |
| 9 |
License URI: https://www.gnu.org/licenses/gpl-2.0.html |
| 10 |
|
| 11 |
Premium WordPress Security - 100% FREE: Firewall, 2FA, Security Headers, Login and Malware Protection, File Monitor, Security Audit & more |
| 12 |
|
| 13 |
== Description == |
| 14 |
|
| 15 |
### Premium Security. Zero Cost. |
| 16 |
|
| 17 |
Vigilant provides enterprise-level WordPress security features completely free. No premium version, no upsells, no hidden features behind paywalls. |
| 18 |
|
| 19 |
Protect your site with a complete security suite: firewall, two-factor authentication, brute force protection, security headers, file integrity monitoring, closed plugin detection, malware detection, user management, security audit logging, under attack mode and much more. |
| 20 |
|
| 21 |
Once activated, Vigilant immediately applies firewall rules against common attacks (SQL injection, XSS, file inclusion), security headers, login attempt monitoring, XML-RPC blocking, WordPress version hiding and sensitive file protection (.htaccess, wp-config.php), after automatically backing up your existing configuration files. |
| 22 |
|
| 23 |
### One-Click Security Presets |
| 24 |
|
| 25 |
Choose a preset and get protected instantly: |
| 26 |
|
| 27 |
**Standard** - Balanced security suitable for most websites. Enables all modules with sensible defaults that won't interfere with normal site operation. |
| 28 |
|
| 29 |
**Maximum Security** - Strictest settings for high-security sites. Tighter rate limits, stronger CSP rules, mandatory admin notifications. May require fine-tuning for some setups. |
| 30 |
|
| 31 |
You can always customize individual settings after applying a preset. |
| 32 |
|
| 33 |
== Under Attack Mode == |
| 34 |
|
| 35 |
Is your site under active attack? Activate Under Attack mode with one click and stop malicious traffic instantly: |
| 36 |
|
| 37 |
* **JavaScript challenge** - Every visitor must pass an automatic browser verification before accessing your site. Real browsers solve it in seconds, bots get blocked completely |
| 38 |
* **Aggressive rate limiting** - Requests limited to 30 per minute with 15-minute blocks for offenders |
| 39 |
* **HTTP method restriction** - Only GET, POST and HEAD allowed; PUT, DELETE, PATCH, OPTIONS and TRACE are blocked |
| 40 |
* **Empty user agent blocking** - Requests without a user agent header are rejected |
| 41 |
* **Full XML-RPC lockdown** during the attack |
| 42 |
* **REST API restriction** - Only authenticated users can access the REST API |
| 43 |
* **Auto-deactivation** - Mode turns off after 4 hours so you never forget it's on |
| 44 |
* **Email notifications** when the mode activates and deactivates |
| 45 |
* **HMAC-signed cookies** - Verified visitors get a signed cookie so they only see the challenge once |
| 46 |
|
| 47 |
Under Attack mode works independently from your preset configuration. Your regular settings are preserved and restored when the mode deactivates. |
| 48 |
|
| 49 |
== Two-Factor Authentication (2FA) == |
| 50 |
|
| 51 |
Add a second verification step to your WordPress login: |
| 52 |
|
| 53 |
* **Authenticator app (TOTP)** - Google Authenticator, Authy, Microsoft Authenticator or any TOTP-compatible app |
| 54 |
* **Email codes** - One-time 6-digit verification codes sent via email |
| 55 |
* QR code setup directly in user profiles |
| 56 |
* 10 backup codes for emergency access if you lose your device |
| 57 |
* Configurable grace period for users to set up their authenticator app |
| 58 |
* Trusted devices - optionally let users skip 2FA on recognized devices for 30 days |
| 59 |
* Role-based enforcement - require 2FA for administrators, editors or any role |
| 60 |
* Exclude specific users from 2FA requirements |
| 61 |
* Admin tool to reset TOTP for users who lost their authenticator |
| 62 |
* Configurable code expiry, attempt limits and email sender name |
| 63 |
* User notification emails when 2FA is enabled or the method changes |
| 64 |
|
| 65 |
== Firewall Protection == |
| 66 |
|
| 67 |
Block malicious requests before they reach WordPress: |
| 68 |
|
| 69 |
* SQL injection blocking |
| 70 |
* XSS (Cross-Site Scripting) attack prevention |
| 71 |
* File inclusion protection (LFI/RFI) |
| 72 |
* Directory traversal blocking |
| 73 |
* Bad query string filtering (catches generic suspicious patterns the specific blockers miss) |
| 74 |
* Bad bot detection and blocking |
| 75 |
* Block requests with empty user agent |
| 76 |
* Rate limiting against DDoS and brute force, with optional progressive lockouts |
| 77 |
* IP whitelist and blacklist management (IPv4 and IPv6, with CIDR ranges and wildcards) |
| 78 |
* User-Agent whitelist and blacklist with partial matching |
| 79 |
* Visitor IP detection control - read the real IP directly from the connection (a spoof-proof default) or from a proxy header when behind Cloudflare, a reverse proxy or a load balancer, with an admin notice if a proxy is detected but not configured |
| 80 |
* HTTP method restriction |
| 81 |
* Server-level file protection via .htaccess: block direct access to wp-config.php, .htaccess, wp-includes/ and sensitive files (.log, .sql, .bak, .ini, debug.log, readme.html, etc.), and optionally wp-cron.php external access |
| 82 |
* Block PHP execution in /uploads (one of the most common post-exploit vectors) |
| 83 |
* Disable directory browsing |
| 84 |
|
| 85 |
== Login Security == |
| 86 |
|
| 87 |
Stop unauthorized access attempts: |
| 88 |
|
| 89 |
* Limit login attempts with configurable thresholds |
| 90 |
* Progressive lockouts - longer blocks for repeat offenders |
| 91 |
* Custom login URL - hide wp-login.php from bots |
| 92 |
* Login URL change notifications to all admin-area users |
| 93 |
* Hide login error messages - don't reveal valid usernames |
| 94 |
* XML-RPC control: leave it on, block only the pingback methods (recommended, it closes the amplification vector while the mobile app and Jetpack keep working), or disable it completely |
| 95 |
* Application passwords control |
| 96 |
* Email notification when an IP is blocked for exceeding login attempts |
| 97 |
* Admin login notifications via email |
| 98 |
* IP whitelist for trusted locations |
| 99 |
|
| 100 |
== User Security == |
| 101 |
|
| 102 |
Comprehensive user account protection: |
| 103 |
|
| 104 |
* Block insecure usernames (admin, test, root, etc.) on new registrations |
| 105 |
* Warn about existing users with insecure usernames so you can rename or remove them |
| 106 |
* Block author scanning - intercept `?author=N` URLs so WordPress doesn't redirect them to `/author/USERNAME/` and leak the login slug |
| 107 |
* Force strong passwords with minimum length |
| 108 |
* Password expiration with configurable intervals |
| 109 |
* Password history - prevent reusing old passwords |
| 110 |
* Force password reset - by specific users, by role, or all users (post-hack recovery) |
| 111 |
* Session limits - control concurrent logins per user |
| 112 |
* Session management - view and revoke active sessions |
| 113 |
* Email verification for new registrations |
| 114 |
* Registration approval workflow - manually approve new users |
| 115 |
* Admin account monitoring - alerts for new admins, email changes, password changes, privilege escalation |
| 116 |
* Display name protection - prevent exposing login username publicly |
| 117 |
|
| 118 |
== Security Headers == |
| 119 |
|
| 120 |
Achieve Grade A security ratings: |
| 121 |
|
| 122 |
* Content Security Policy (CSP) with a WordPress-compatible default policy and Report-Only mode for safe testing before enforcing |
| 123 |
* HSTS (HTTP Strict Transport Security) with includeSubdomains and preload options |
| 124 |
* X-Frame-Options - prevent clickjacking |
| 125 |
* X-Content-Type-Options - prevent MIME sniffing |
| 126 |
* Referrer Policy control |
| 127 |
* Permissions Policy (camera, microphone, geolocation, payment, USB) |
| 128 |
* Cross-Origin policies (COEP, COOP, CORP) |
| 129 |
* HTTPS enforcer with automatic mixed content fix |
| 130 |
* Server fingerprint hiding - the `Server:` header is neutralized and `X-Powered-By` and other fingerprinting headers are stripped from responses |
| 131 |
|
| 132 |
== File Integrity Monitoring == |
| 133 |
|
| 134 |
Detect unauthorized changes to your files and compromised plugins: |
| 135 |
|
| 136 |
* WordPress core verification against official checksums |
| 137 |
* Plugin and theme file monitoring with WordPress.org checksums |
| 138 |
* Critical config files (wp-config.php, .htaccess) monitored against baseline, detecting code injection even in files with no official checksum |
| 139 |
* Closed and removed plugins detection - daily check against the WordPress.org repository, flagging any installed plugin closed for malware, security issues or guideline violations, including both explicit closures and silent "removed" takedowns, with per-slug Ignore for legacy plugins you can't uninstall yet |
| 140 |
* Line-level diff view of changes, with per-file approval workflow |
| 141 |
* Suspicious code scanning for plugins and themes without checksums |
| 142 |
* Extra file detection in plugins and themes (files not in original distribution) |
| 143 |
* Uploads directory scanning for PHP files, double extensions and .htaccess, with smart classification of dangerous rules vs protective ones |
| 144 |
* Root directory scanning for non-core PHP files (common attack vector) |
| 145 |
* String concatenation obfuscation detection |
| 146 |
* Configurable notification levels and an ignore list to dismiss known files |
| 147 |
* Excluded paths and file extensions |
| 148 |
* Scheduled automatic scans (daily, weekly) |
| 149 |
* HTML formatted email alerts with severity sections, including a dedicated section for closed plugins |
| 150 |
|
| 151 |
== Security Audit == |
| 152 |
|
| 153 |
Track everything happening on your site: |
| 154 |
|
| 155 |
* Successful and failed login attempts |
| 156 |
* Two-factor authentication events |
| 157 |
* User account changes (creation, deletion, role changes) |
| 158 |
* Content modifications (posts, pages) |
| 159 |
* Plugin and theme activations/deactivations |
| 160 |
* Security events and blocked threats |
| 161 |
* HTTP request method tracking and filtering (GET, POST, PUT, DELETE) |
| 162 |
* Enhanced log detail popup with grouped sections and quick actions |
| 163 |
* One-click add IP or User-Agent to firewall whitelist/blacklist from log entries |
| 164 |
* Direct IP lookup links to AbuseIPDB |
| 165 |
* Configurable retention period, CSV export, and filtering by event type, severity, request method or date |
| 166 |
|
| 167 |
**Audit Alerts** - get an email when the audit log points to something worth your attention, off by default and configured under Security Audit: |
| 168 |
|
| 169 |
* Immediate alerts the moment a serious event is logged, by minimum severity (a new administrator, a closed plugin or a privilege escalation are all logged as Critical) |
| 170 |
* Threshold alerts when a category spikes - firewall blocks, login failures, user, plugin, file integrity, security, system and content events - over a 30-minute, 1, 6 or 24 hour window, counting only warning and critical events so routine activity never trips them |
| 171 |
* A single anti-repeat cooldown keeps a storm of events down to one notice instead of flooding your inbox |
| 172 |
* Active alerts surface in Settings & Tools, the Dashboard, the Configuration Score and the Security Check |
| 173 |
* "Send test email" button to confirm delivery |
| 174 |
|
| 175 |
== Security Check == |
| 176 |
|
| 177 |
On-demand security audit built into the Dashboard. No external services, no accounts, no API keys - everything runs on your server: |
| 178 |
|
| 179 |
* 40+ checks across 6 categories: SSL/TLS, HTTP Headers, WP Exposure, Access & Auth, Sensitive Files and Internal Checks |
| 180 |
* Single 0-100 score with A-E grade, plus per-category breakdown and explanatory details for every check |
| 181 |
* 15 exclusive internal checks impossible from the outside: PHP end-of-life status, pending updates, inactive plugins, closed or removed plugins, file permissions, default salts detection, `wp_` table prefix, `admin` username, administrators without 2FA enrolled, module status, recent audit errors, last File Integrity scan result and whether audit alerts are configured |
| 182 |
* DNS-only reputation lookup against Spamhaus ZEN, Barracuda BRBL and SpamCop SCBL (informational - listings are flagged but don't deduct from the score) |
| 183 |
* Two-phase scan: fast local checks appear in under a second, remote checks stream in as they complete |
| 184 |
* Weekly automatic scan with opt-in email alert if the score drops by 10+ points or a new critical check starts failing |
| 185 |
* 30-scan history with sparkline trend and delta chip |
| 186 |
* "Go to setting" fix link on every failing check, jumping straight to the exact Vigilant field that resolves it |
| 187 |
* Smart header diagnostics that report "configured but not being served" when a cache/CDN overrides your headers |
| 188 |
|
| 189 |
== WordPress Hardening == |
| 190 |
|
| 191 |
Layered protection at the WordPress level - admin, content, head, feeds and database: |
| 192 |
|
| 193 |
* Lock down the admin: disable the built-in plugin and theme file editor, block installations and updates from the admin area, and force HTTPS for the admin area. Compatible with any hosting layout, respecting values already in place and never overriding them |
| 194 |
* Disable WordPress's internal page-view cron when you already have a real server-side cron job configured |
| 195 |
* Dashboard warning when debug mode is left enabled in production, so error output never leaks to visitors |
| 196 |
* Hide your WordPress version everywhere it can leak: from the HTML head, from RSS and Atom feeds, and optionally from every script and style URL on the front-end (stripping only the WordPress version itself, leaving plugin and theme cache busting intact) |
| 197 |
* Automatic daily removal of readme.html, license.txt and licencia.txt from the WordPress root, which otherwise expose your version |
| 198 |
* HTML head cleanup - remove the RSD link, Windows Live Writer manifest, shortlink header and REST API discovery link |
| 199 |
* Database hardening - check for the default `wp_` table prefix and one-click rename tool with full backup before the change |
| 200 |
* Comment security - honeypot field against spam bots, force moderation on every new comment, close comments on old posts, disable pingbacks and trackbacks |
| 201 |
* Feed management - completely disable RSS and Atom feeds, or only disable them when the site has no published content |
| 202 |
|
| 203 |
== REST API Security == |
| 204 |
|
| 205 |
Control API access to your site: |
| 206 |
|
| 207 |
* Three access modes: public (default WordPress behavior), authenticated only (closes the API to anonymous visitors), or selective (custom allow/block lists) |
| 208 |
* Block user enumeration via `/wp-json/wp/v2/users` |
| 209 |
* Protect any list of sensitive endpoints from anonymous access |
| 210 |
* Per-plugin compatibility toggles so authenticated mode doesn't break the front-end: WooCommerce, Contact Form 7, Gravity Forms, WPForms, Elementor, Jetpack. oEmbed and Site Health endpoints stay accessible by default |
| 211 |
|
| 212 |
== Security Tools == |
| 213 |
|
| 214 |
Utilities included: |
| 215 |
|
| 216 |
* **Database Backup** - Download a full or partial database backup as ZIP with table selection |
| 217 |
* **Database Prefix Change** - Change the default wp_ prefix to a random secure prefix |
| 218 |
* **Export/Import Settings** - Transfer your configuration between sites |
| 219 |
* **Manual Backup** - Create backups of .htaccess and wp-config.php on demand |
| 220 |
* **Reset to Defaults** - Start fresh with one click |
| 221 |
|
| 222 |
== Safe by Design == |
| 223 |
|
| 224 |
Your existing .htaccess, wp-config.php and robots.txt are automatically backed up before any modifications. Backups are stored in the WordPress database, never as files under the web root, and verified with MD5 checksums. |
| 225 |
|
| 226 |
When you deactivate Vigilant, all security rules are automatically removed and your original configuration files are restored. No leftover code, no broken sites. |
| 227 |
|
| 228 |
== Why Vigilant? == |
| 229 |
|
| 230 |
Most WordPress security plugins reserve their best features for paid plans. Vigilant gives you everything upfront - no premium tier, no feature locks, no upsells. Firewall, 2FA with authenticator app, security headers, file integrity scanner, security audit, on-demand Security Check with weekly regression alerts, and more. All free, all maintained, all following WordPress coding standards. |
| 231 |
|
| 232 |
We maintain a detailed feature comparison between Vigilant and other popular security plugins (Wordfence, Solid Security, AIOS, Sucuri, SG Security). See what each offers in its free version and where Vigilant fills the gaps. |
| 233 |
|
| 234 |
→ [View the full comparison](https://vigilante.works/comparison.html) |
| 235 |
|
| 236 |
== Installation == |
| 237 |
|
| 238 |
1. Upload the plugin files to `/wp-content/plugins/vigilante/` or install directly from the WordPress plugin repository |
| 239 |
2. Activate the plugin through the 'Plugins' menu in WordPress |
| 240 |
3. Go to 'Vigilant' in the admin menu |
| 241 |
4. Apply a security preset or customize individual module settings |
| 242 |
|
| 243 |
**Requirements:** |
| 244 |
|
| 245 |
* WordPress 6.2 or higher |
| 246 |
* PHP 7.4 or higher |
| 247 |
* Apache or LiteSpeed server (for .htaccess features) |
| 248 |
* SSL certificate recommended for HSTS |
| 249 |
|
| 250 |
== Frequently Asked Questions == |
| 251 |
|
| 252 |
= Will this plugin slow down my site? = |
| 253 |
|
| 254 |
No. Vigilant is optimized for performance. The firewall uses efficient pattern matching, database queries are cached with transients, and .htaccess rules execute at server level before PHP even loads. |
| 255 |
|
| 256 |
= What happens when I activate the plugin? = |
| 257 |
|
| 258 |
Vigilant immediately backs up your existing .htaccess and wp-config.php to the database, then applies default security settings. All modules are enabled with balanced defaults suitable for most sites. |
| 259 |
|
| 260 |
= What happens when I deactivate the plugin? = |
| 261 |
|
| 262 |
All security modifications are automatically reverted. The .htaccess rules are removed, wp-config.php constants are restored to their original values, and scheduled tasks are cleared. Your site returns to its pre-Vigilant state. |
| 263 |
|
| 264 |
= How does two-factor authentication work? = |
| 265 |
|
| 266 |
Vigilant supports two 2FA methods. With the **authenticator app** (TOTP), you scan a QR code in your profile to link an app like Google Authenticator or Authy, then enter a 6-digit code from the app on every login. With **email codes**, you receive a one-time code via email after entering your password. If enabled by the site administrator, you can mark your device as trusted to skip 2FA for 30 days. |
| 267 |
|
| 268 |
= What if I lose my phone or authenticator app? = |
| 269 |
|
| 270 |
When you set up TOTP, Vigilant generates 10 backup codes. You can use any of them as a one-time replacement for the authenticator code. If you run out of backup codes, an administrator can reset your TOTP from the plugin settings. |
| 271 |
|
| 272 |
= What if I don't receive the 2FA email code? = |
| 273 |
|
| 274 |
Check your spam folder first. You can click "Resend code" on the verification form. Codes expire after 10 minutes by default. If issues persist, an administrator can temporarily disable 2FA from the plugin settings. |
| 275 |
|
| 276 |
= Can I switch between email and authenticator app? = |
| 277 |
|
| 278 |
Yes. Go to Login Security > Two-Factor Authentication and change the verification method. If notifications are enabled, affected users will receive an email explaining the new method and how to set it up. |
| 279 |
|
| 280 |
= Which user roles require 2FA? = |
| 281 |
|
| 282 |
By default, 2FA is enforced for administrators and editors. You can customize which roles require 2FA in the Login Security settings, and exclude specific users individually. |
| 283 |
|
| 284 |
= How do I recover if I'm locked out? = |
| 285 |
|
| 286 |
Access your site via FTP/SFTP and either rename the plugin folder to disable it temporarily, or delete the `vigilante_login_attempts` table rows for your IP address in the database. |
| 287 |
|
| 288 |
= Will the firewall block legitimate users? = |
| 289 |
|
| 290 |
The firewall is configured to allow normal WordPress operations, including the block editor, REST API, and popular page builders. If you experience issues, you can whitelist specific IPs or adjust rate limiting thresholds. |
| 291 |
|
| 292 |
= Can I use this with other security plugins? = |
| 293 |
|
| 294 |
While Vigilant works standalone, running multiple security plugins can cause conflicts. We recommend testing in a staging environment first if you need to combine security solutions. |
| 295 |
|
| 296 |
= Does this work with caching plugins? = |
| 297 |
|
| 298 |
Yes. Vigilant is compatible with popular caching plugins. The firewall runs before cache layers, and .htaccess rules don't interfere with caching mechanisms. |
| 299 |
|
| 300 |
= Does this work with WooCommerce? = |
| 301 |
|
| 302 |
Yes. Vigilant includes compatibility settings for WooCommerce. The REST API security module automatically allows WooCommerce endpoints, and the firewall won't block payment gateway connections. |
| 303 |
|
| 304 |
= How do I test my security headers? = |
| 305 |
|
| 306 |
Use the built-in header testing tool in the Security Headers tab, or visit securityheaders.com with your site URL to get a security grade. |
| 307 |
|
| 308 |
= What is Security Check? = |
| 309 |
|
| 310 |
Security Check is an on-demand audit built into the Dashboard. It runs 40+ checks across 6 categories (SSL/TLS, HTTP headers, WordPress exposure, access and authentication, sensitive files, and internal checks) and returns a 0–100 score with an A–E grade. Unlike external online scanners, it runs entirely on your server and has access to 14 exclusive internal checks: PHP end-of-life status, pending updates, closed/removed plugins, file permissions, default salts detection, administrators without 2FA enrolled, and more. |
| 311 |
|
| 312 |
= Does Security Check send my data to an external service? = |
| 313 |
|
| 314 |
No. All checks run on your server. The only external traffic is three DNS-only lookups against public blacklists (Spamhaus, Barracuda, SpamCop) for the reputation category — these are standard DNS queries with no authentication, no API keys, and no payload beyond your site's IP address. If you disable the reputation category, Security Check makes zero external network calls. |
| 315 |
|
| 316 |
= How often should I run Security Check? = |
| 317 |
|
| 318 |
Run it manually after any significant change (plugin update, server migration, new user role configuration). For ongoing monitoring, enable the weekly automatic scan from the widget. You'll only receive an email if the score drops by 10 points or more, or if a new critical check starts failing — so no spam from routine scans. |
| 319 |
|
| 320 |
= What is password expiration? = |
| 321 |
|
| 322 |
You can require users to change their passwords after a set number of days (30, 60, 90, etc.). Users receive warnings before expiration and are forced to change their password on next login when it expires. Password history prevents reusing recent passwords. |
| 323 |
|
| 324 |
= What is registration approval? = |
| 325 |
|
| 326 |
When enabled, new user registrations require manual approval by an administrator before the account becomes active. Pending users cannot log in until approved. You can configure auto-rejection after a set number of days. |
| 327 |
|
| 328 |
= What does email verification do? = |
| 329 |
|
| 330 |
New users must verify their email address by clicking a link before their account becomes active. This prevents fake registrations and ensures valid contact information. |
| 331 |
|
| 332 |
= How do session limits work? = |
| 333 |
|
| 334 |
You can limit how many concurrent sessions each user can have. When the limit is reached, either the new login is blocked or the oldest session is terminated, depending on your configuration. |
| 335 |
|
| 336 |
= Can I export the security audit log? = |
| 337 |
|
| 338 |
Yes. The security audit log can be exported to CSV format for external analysis or compliance reporting. You can also filter logs by event type, user, or date range before exporting. |
| 339 |
|
| 340 |
= What files does the integrity scanner check? = |
| 341 |
|
| 342 |
The scanner compares WordPress core files, plugin files, and theme files against official checksums from WordPress.org. Plugins and themes without available checksums are also scanned using strict obfuscation pattern detection. The uploads directory is scanned for PHP files, double extensions, and .htaccess files. Extra PHP files not present in original distributions are detected and, if they contain suspicious code, automatically flagged as suspicious. |
| 343 |
|
| 344 |
= How often does the file integrity scan run? = |
| 345 |
|
| 346 |
You can configure automatic scans to run daily or weekly. You can also run manual scans at any time. Email notifications support three levels: all issues, suspicious files only, or disabled. |
| 347 |
|
| 348 |
= What is the difference between Standard and Maximum presets? = |
| 349 |
|
| 350 |
Standard applies balanced settings suitable for most sites. Maximum applies stricter rules: lower rate limits, tighter CSP policies, required admin notifications, session limits, and more aggressive hardening. Maximum may require adjustments for sites with complex functionality. |
| 351 |
|
| 352 |
= Where are backups stored? = |
| 353 |
|
| 354 |
Configuration backups (.htaccess, wp-config.php, robots.txt) are stored in the WordPress database, not as files under the web root, so they can never be served over HTTP. A database backup you download is generated as a temporary ZIP with an unguessable name and removed right after the download. |
| 355 |
|
| 356 |
= What is Under Attack mode? = |
| 357 |
|
| 358 |
Under Attack mode is an emergency feature you can activate when your site is experiencing an active attack. It adds a JavaScript challenge that real browsers solve automatically in a few seconds, while bots and automated scripts are blocked completely. It also applies aggressive rate limiting, blocks restricted HTTP methods, and restricts API access. |
| 359 |
|
| 360 |
= Will Under Attack mode affect my logged-in users? = |
| 361 |
|
| 362 |
No. Logged-in users, admin pages, cron jobs, AJAX requests, and the login page are all excluded from the JavaScript challenge. Only unauthenticated frontend visitors see the verification page. |
| 363 |
|
| 364 |
= What if I forget to turn off Under Attack mode? = |
| 365 |
|
| 366 |
It automatically deactivates after 4 hours. You will also receive an email notification when it activates and deactivates. |
| 367 |
|
| 368 |
= Does Under Attack mode change my regular security settings? = |
| 369 |
|
| 370 |
No. It operates independently from your preset configuration (Standard or Maximum). Your regular settings are untouched and continue working normally after Under Attack mode deactivates. |
| 371 |
|
| 372 |
= How does the database backup work? = |
| 373 |
|
| 374 |
Go to Vigilant > Tools > Database Backup. Select which tables to include (or leave all selected), then click Download. The backup is generated as a temporary ZIP with an unguessable name, streamed to your browser and deleted from the server immediately after the download. |
| 375 |
|
| 376 |
= What does changing the database prefix do? = |
| 377 |
|
| 378 |
WordPress uses wp_ as default table prefix. Changing it to a random prefix adds a layer of protection against SQL injection attacks that target default table names. Go to Vigilant > WP Hardening > Database Hardening. Always create a backup before changing the prefix. |
| 379 |
|
| 380 |
= How do I exclude management services like ManageWP from the firewall? = |
| 381 |
|
| 382 |
Go to Vigilant > Firewall > User-Agent Lists and add the service name (e.g., ManageWP, MainWP, UptimeRobot) to the User-Agent Whitelist. Partial matching is used, so entering "ManageWP" will match any User-Agent string containing that keyword. |
| 383 |
|
| 384 |
If you also use a custom login URL, add the management dashboard's IP address to the firewall IP Whitelist as well. Some operations (for example pushing a plugin update from MainWP) reach wp-admin without a WordPress session and with a generic WordPress user agent rather than the service name, so the User-Agent rule alone would not match them. A whitelisted IP is allowed past the hidden login/wp-admin protection (it still has to authenticate). |
| 385 |
|
| 386 |
= Can I send security notifications to someone other than the site admin? = |
| 387 |
|
| 388 |
Yes. Go to Vigilant > Settings & Tools > Notification settings. You can add additional email recipients (one per line) and optionally uncheck the WordPress admin email. This is useful for maintenance professionals managing multiple sites who need to receive all security alerts. |
| 389 |
|
| 390 |
= Can I customize notification recipients programmatically? = |
| 391 |
|
| 392 |
Yes. Use the `vigilante_notification_recipients` filter. It receives and returns an array of email addresses used for all administrative notifications: |
| 393 |
|
| 394 |
`add_filter( 'vigilante_notification_recipients', function( $recipients ) { |
| 395 |
$recipients[] = 'security-team@example.com'; |
| 396 |
return $recipients; |
| 397 |
} );` |
| 398 |
|
| 399 |
== Screenshots == |
| 400 |
|
| 401 |
1. Security Dashboard - Security score, module controls, and preset selection |
| 402 |
2. Two-Factor Authentication - Second verification step during login |
| 403 |
3. Login Security - Brute force protection, 2FA, lockouts, and custom login URL |
| 404 |
4. User Security - Complete user protection tools and settings |
| 405 |
5. Password Expiration - Force periodic password changes with history |
| 406 |
6. Registration Approval and Session Limits - Control new users and concurrent logins |
| 407 |
7. File Integrity - Scanner settings and verification results |
| 408 |
8. Security Audit - Filterable event viewer with export option |
| 409 |
9. Database Backup - Download full or partial database backups with table selection |
| 410 |
10. Security Check - On-demand audit widget with score, per-category breakdown, and fix links |
| 411 |
|
| 412 |
== Changelog == |
| 413 |
|
| 414 |
= 2.11.2 = |
| 415 |
* Improved: the User-Agent whitelist no longer skips the whole firewall. It still keeps a remote manager such as ManageWP or MainWP from being turned away by the bot rules, which is what it is for, but a request carrying a whitelisted agent is now checked for SQL injection, script injection, remote file inclusion, traversal and HTTP method like any other. A header the client chooses cannot stand in for an identity: anyone who guessed a configured substring walked past every one of those rules. The list is empty unless you filled it in, so only sites that had configured one were affected. |
| 416 |
* Improved: Under Attack mode resolves the visitor address through the same helper as the firewall, honouring the trusted proxy header you configured instead of believing CF-Connecting-IP or X-Forwarded-For from whoever sends them. Those four things it decides with that address, the whitelist, the challenge nonce, the verification cookie and the rate limit exemption, could be steered by sending an invented header. If your site is behind Cloudflare or a reverse proxy, set the trusted proxy header in the firewall settings so both modules see the real client address. |
| 417 |
* Fix: the integrity baseline no longer keeps the contents of wp-config.php in the database. It stored the whole file so it could show which lines changed, which meant the database password and the eight authentication keys and salts sat in an option, within reach of anyone who later read the database or a backup of it. Credential values are replaced with a marker before the copy is stored, the file hash still covers the whole file so a change to a secret is still detected, and the copy already saved on your site is cleaned on the first admin page load after updating. If a secret cannot be removed from the copy for any reason, nothing is stored and the scan reports the change without a line diff. |
| 418 |
|
| 419 |
= 2.11.1 = |
| 420 |
* Improved: the buttons in the notification emails land on the exact section they talk about. The file integrity email opens the last scan results, the plugin status one the closed and removed plugins list, the lockout one the login protection status and the Under Attack one its own panel, instead of leaving the reader at the top of a tab. |
| 421 |
* Improved: a firewall block on a REST API route answers with JSON instead of the HTML Forbidden page, so the block editor and any other REST client can show what actually happened. Same status code, same message, the envelope core uses for an error. |
| 422 |
* Fix: the remote file inclusion rule no longer stops the block editor from embedding. An external URL in any parameter was the whole signature, and that is the shape of a link rather than of an inclusion: the block editor asks core to resolve the pasted URL through /wp-json/oembed/1.0/proxy, so embedding a video was refused with a 403 on every site with the rule on, while the classic editor kept working because it posts that URL instead of putting it in the address. A URL now counts as an inclusion attempt when it travels in a parameter that is read as a path, or when it points at something includable. Core's embed proxy is exempt for users who can edit posts, which is what that endpoint requires anyway. The same false positive turned away a search for a URL and any return_url or redirect parameter. |
| 423 |
* Fix: the address of a blocked request is recorded as it arrived. It went through a sanitiser that deletes percent encoded characters instead of decoding them, so a blocked embed was stored as httpswww.youtube.comwatchv and there was no way to tell from the log what had been blocked. |
| 424 |
* Fix: the activity log detail shows the address of a firewall block. Every one of them was recorded under a key the log screen does not read, so that field was empty for the module that logs the most and diagnosing a block meant reading the database by hand. Entries recorded before this update show it too, and a block by blacklisted address now records the address as well. |
| 425 |
* Fix: the links that point at a setting now land on that setting. Fifteen of the 42 Fix links in the Security Check, and the notice about users awaiting approval, used anchors that are not in the page: four still carried the name the firewall section had before it was renamed to Server Protection in 2.0.0, and two pointed at a Tools section that does not exist, when what resolves those findings lives in the firewall. A link like this fails silently, because the browser simply stays where it is, so it looks like the link was always meant to work that way. The link in the weekly report email was ignored by the highlight code as well, so it neither scrolled nor flashed on arrival. |
| 426 |
|
| 427 |
= 2.11.0 = |
| 428 |
* New: the activity log export now carries the action, the address and the User-Agent of every entry, and every column neutralises spreadsheet formulas and doubles quotes, not only the message. |
| 429 |
* Improved: a remembered device is recognised by a random secret kept in an HttpOnly cookie, not by its User-Agent. Knowing the browser string of a remembered device was enough to skip the second factor once the password was known. Every device remembered before this update has to pass the second factor once more. |
| 430 |
* Improved: the remember-this-device option is enforced on the server. With it off, no stored device is honoured and none is saved, whatever the form sends. |
| 431 |
* Improved: the authenticator code has an attempt limit per pending session and accepts one time step of clock drift instead of two. Nothing counted those attempts before, because the lockout runs on the authenticate filter and the verification form never passes through it. |
| 432 |
* Improved: the login screen no longer says whether an account exists, is waiting for approval, has an unverified email or has too many sessions. All of these show the same generic message now, since each of them was only shown once the password was right. |
| 433 |
* Improved: application passwords are no longer blocked by the second factor, which they already are on their own. A REST or XML-RPC login with the main password is still refused, but without sending a code or opening a verification session, so a connector that retries no longer causes one email per attempt. |
| 434 |
* Improved: on a network, Under Attack mode no longer rewrites the shared .htaccess from a subsite. That part is reserved to a network administrator on the main site, and the rest of the mode stays available on every subsite. The rewrite goes through the same locked and verified path as the other blocks Vigilant writes, and a failure in that step is recorded in the activity log instead of being swallowed. On a host where WordPress cannot write files directly, those cache rules are skipped and recorded, as every other block Vigilant writes already was; the rest of the mode is unaffected, and the admin notice shows the block to add to the .htaccess by hand. |
| 435 |
* Improved: uninstalling on a network cleans the tables and options of every site, not only the one running the uninstall. |
| 436 |
* Improved: the firewall keeps the active rate-limit block in a transient per address and reads that on every request, instead of loading the whole list of blocked addresses, which had no upper bound and grew with every new address of a distributed attack. The list the Firewall tab shows is capped at 500 entries. A block that was active at the moment of the update is not carried over: that address has to exceed the limit again to be blocked. |
| 437 |
* Fix: the second factor can no longer be skipped through a login form other than wp-login.php. Both modules let a request through when it carried the verification action, the form nonce and a pending session token, but all three are within reach of whoever knows the password: the nonce is printed on the verification form and the token is issued to the visitor who just sent the password. On wp-login.php that request is routed to the verification handler and stopped, but any other form that calls wp_signon(), the WooCommerce login among them, reached the authentication filter and completed the login without a code. The shortcut is gone: the only path that completes a login with the second factor is the verification handler itself. Found in the cross review of this release and reproduced against 2.10.5. |
| 438 |
* Fix: the login lockout works on sites whose timezone is not UTC. The attempts table stored the time of the last attempt in local time and the lockout expiry in UTC, and compared them against each other, so with a positive offset the lockout was never seen as active and with a negative one the attempts were never counted. Present since 1.0.0, found while testing this release. |
| 439 |
* Fix: an address that is already locked out no longer receives a new lockout, a new critical entry and a new email on every attempt made during the lockout. |
| 440 |
* Fix: a pending second-factor session is no longer indexed by IP address. Behind a proxy or a CDN, where visitors share an apparent address, one visitor could be handed the pending session of another user together with the form to complete it. |
| 441 |
* Fix: a verification form submitted with an expired nonce explains what happened and records the attempt, instead of silently redrawing the form. |
| 442 |
* Fix: the settings import discards any section or key outside the plugin schema instead of merging it into the stored configuration. Saving from the settings screen applies the same rule. |
| 443 |
* Fix: email verification codes are stored hashed, and the authenticator secret requires the AUTH_KEY security key to be defined instead of falling back to a value written in the code. |
| 444 |
|
| 445 |
For older changelog entries, please check the [changelog.txt](https://plugins.svn.wordpress.org/vigilante/trunk/changelog.txt) file |
| 446 |
|
| 447 |
== Upgrade Notice == |
| 448 |
|
| 449 |
= 2.11.2 = |
| 450 |
Security release. The User-Agent whitelist no longer skips the firewall, Under Attack resolves the visitor address through your trusted proxy setting, and wp-config.php secrets are no longer kept in the database. |
| 451 |
|
| 452 |
== Support == |
| 453 |
|
| 454 |
Need private support or custom development? |
| 455 |
|
| 456 |
Do you need one-on-one help, priority troubleshooting, or a custom feature, integration, or tweak built specifically for your site? I offer private support and custom development. Just [contact me](mailto:vigilante@ayudawp.com) and tell me what you need. |
| 457 |
|
| 458 |
Need help or have suggestions? |
| 459 |
|
| 460 |
* [Official website](https://servicios.ayudawp.com/) |
| 461 |
* [WordPress support forum](https://wordpress.org/support/plugin/vigilante/) |
| 462 |
* [YouTube channel](https://www.youtube.com/AyudaWordPressES) |
| 463 |
* [Documentation and tutorials](https://ayudawp.com/) |
| 464 |
|
| 465 |
Love the plugin? Please leave us a 5-star review and help spread the word! |
| 466 |
|
| 467 |
== About AyudaWP == |
| 468 |
|
| 469 |
We are specialists in WordPress security, SEO, AI and performance optimization plugins. We create tools that solve real problems for WordPress site owners while maintaining the highest coding standards and accessibility requirements. |
| 470 |
|
