| 开发者 | jbsabit |
|---|---|
| 更新时间 | 2026年10月17日 09:20 |
| 捐献地址: | 去捐款 |
| PHP版本: | 7.4 及以上 |
| WordPress版本: | 7.1 |
| 版权: | GPLv2 or later |
| 版权网址: | 版权信息 |
REMOTE_ADDR only, so attackers can't dodge it by spoofing X-Forwarded-For headersX-Frame-Options, X-Content-Type-Options, and Referrer-Policy headers on admin screenswp_hash_password() and verified server-side only — never stored in plaintext, never shown in settings, never exposed to the browser/wp-content/plugins/defentry/, or install through the WordPress plugins screen.2210 — change it immediately to something only you know).When an administrator, editor, or author logs in from a device Defentry has never seen, the WordPress dashboard is covered by a full-screen overlay asking for the siren stop password — optionally with a siren sound. Every other logged-in user simultaneously sees a red alert banner ("New device login detected") with buttons to trust the device, mute the siren, or take Master Admin action.
Enter the correct siren stop password on the new device and it is trusted permanently. The Master Admin can also trust any device for any user from the alert banner or from Defentry → Manage Trusted Devices.
Only the Master Admin — the one administrator designated in the Defentry settings. This keeps emergency response in a single accountable hand.
The user is added to the blocklist. On their next dashboard visit they are logged out immediately with a notice, and they cannot use wp-admin again until the Master Admin unblocks them from Defentry → Manage Blocked Users.
Browsers block audio until you interact with the page (click, scroll, or press a key). The siren starts after your first interaction. You can mute it at any time from the alert banner, or disable/replace it in the Defentry settings.
Yes. In the Defentry settings you can enable or disable the siren and upload your own MP3. Leave the upload empty to use the built-in siren.
Administrators, editors, and authors. Contributors, subscribers, and customers are never interrupted.
An administrator with database access can delete the scbr_settings row from the wp_options table — the plugin then resets to the default password 2210 with protection OFF, so you can set a new password. Alternatively, temporarily rename the plugin folder via FTP/cPanel to disable it, then set a new stop password in the settings.
No — clearing the cookie generates a brand-new random device ID, which is untrusted by definition, so the overlay appears again. The system fails closed.
No. Device verification and 2FA stop different attacks — a stolen password alone is useless against Defentry, and a stolen device alone is useless against 2FA. Use both.
No. Its scripts and styles load only on wp-admin pages, and only when needed. Visitors to your public site are completely unaffected, and the plugin makes no external HTTP requests.
Yes. Verification happens inside wp-admin, which caching plugins and CDNs don't cache. One honest note: IP-based attempt limiting reads REMOTE_ADDR; behind a reverse proxy or CDN (like Cloudflare) all visitors may share the proxy's IP, so an IP block applies proxy-wide. Device verification itself is unaffected.
Settings are stored per site, not network-wide, and multisite has not been officially tested. It should work per-site; network-wide management isn't included.
Random device IDs (in a browser cookie and per-user metadata), plugin settings (in wp_options), and short-lived transients for login attempts and alerts. Nothing ever leaves your server — no tracking, no telemetry, no third-party calls.
Yes. Verification happens inside wp-admin after login, so it works regardless of how the user logged in.
Defentry detects the missing Master Admin and prompts an administrator to choose a new one. Protection settings are preserved.
Yes — 100% free, GPL-licensed, no premium version, no upsells, no locked features.
phpcs:ignore justifications for the five WordPress.Security.NonceVerification.Recommended warnings — all are false positives (display-only $_GET reads; every state-changing handler verifies its nonce). No behavior change.wrs to scbr for all options, transients, user meta, cookies, and scripts to avoid conflicts with other plugins.