內容簡介
ZEISMO Security 是一款整合 WordPress 防火牆、惡意程式掃描、登入保護及實用加固功能的安全外掛，提供本地安全控制台以保護網站免受攻擊。
【主要功能】
• 監控 SQL 注入、跨站腳本等可疑請求
• 本地檔案完整性比較與掃描
• 登入嘗試限制與失敗歷史記錄
• 暫時與永久 IP 禁止及允許清單
• 可選的 XML-RPC 阻擋與安全標頭
外掛標籤
開發者團隊
② 後台搜尋「ZEISMO Security – Firewall, Malware Scanner & Login Protection」→ 直接安裝（推薦）
原文外掛簡介
ZEISMO Security combines a WordPress firewall, malware scanner, login protection and practical hardening in one local security console.
The plugin starts in monitor mode. It inspects suspicious request patterns and records evidence without blocking visitors. After reviewing the activity on your own site, you can enable blocking by attack category.
Included controls
Request monitoring for SQL injection, cross-site scripting, path traversal, local and remote file inclusion, command injection and scanner patterns.
A weighted risk score with monitor and block modes.
Local file-integrity comparisons for supported files in core directories, plugins and themes.
Local malware pattern scanning with bounded file coverage and scan-limit notices.
Login attempt limiting and failed-login history.
Temporary and permanent IP bans plus an allowlist.
Optional XML-RPC blocking, neutral login errors, REST user-enumeration protection and reduced version exposure.
Optional browser security headers and WordPress file-editor hardening.
Local threat history, activity summaries and critical-event email alerts.
A measured configuration score and WordPress toolbar status.
WordPress malware scanning and file integrity
Run a local scan to review suspicious PHP, JavaScript, iframe, redirect and spam patterns in supported files. Integrity checks compare file hashes with a locally recorded baseline to identify additions, modifications and removals. They do not compare every file against an official clean-copy database. Review the site before accepting a new baseline.
Scans cover supported readable files in wp-admin, wp-includes, the plugins directory and the active theme root. Uploads, the database and root-level files are outside these scan roots. Files over 2 MB, unsupported extensions and symbolic links are excluded. A result with no findings is not proof that the entire website is clean.
A safer first-run flow
New installations begin in monitor mode so administrators can inspect real activity before deciding which categories to block. Review the measured local activity and scan coverage before changing settings.
Local by design
The WordPress.org edition runs its available security controls on your own WordPress site. No account, licence token or remote ZEISMO service is required. Local features in this edition are not restricted by a paid plan.
Blocking is disabled by default. Logged-in editors are excluded from firewall enforcement, and the request filter fails open if it cannot evaluate a request. No security plugin can guarantee that a site will not be compromised.
Read the complete user guide | Product information
Privacy and data handling
This WordPress.org distribution performs its security analysis on the WordPress site where it is installed. It does not contact ZEISMO, load remote code, check a ZEISMO licence, send source files to ZEISMO or include a separate updater.
The plugin stores security settings and local security records in the site’s WordPress database. Records can include request paths, browser user-agent strings, usernames used in login attempts, pseudonymous IP hashes and, when enabled, raw IP addresses. Raw IP storage is enabled by default so administrators can investigate and block attacks. Administrators can disable raw IP storage or anonymise logged addresses in Settings.
Security events follow the retention period selected by the administrator. Raw event IP addresses are removed after 90 days even when a longer event-retention period is selected. Optional critical alerts are sent with the site’s configured WordPress mail system and are disabled by default.
Deactivation feedback is optional, stays in the site’s WordPress database and is not sent to ZEISMO. Deactivating or deleting the plugin preserves settings and security records so an administrator does not lose incident evidence. Site owners who want to remove that data can delete the zeismo_security_settings, zeismo_sec_db_version, zeismo_sec_setup_complete and zeismo_sec_deactivation_feedback options and the database tables whose names begin with their WordPress table prefix followed by zeismo_sec_.
Administrator and security-change alerts
In Settings > Alerts, choose a notification email and opt in to administrator and security-setting changes. Notices cover administrator creation or promotion, selected firewall and login controls, notification settings, and two-factor enable/disable/recovery replacement. They include the site, UTC time and user IDs, never passwords, authenticator keys, recovery codes or account email addresses.
Change notices are disabled by default. They use your site’s WordPress mail system, with a maximum of ten attempts per clock hour and five-minute duplicate suppression. Failed or uncertain attempts are not automatically retried. Settings show the last accepted, failed or suppressed state; acceptance by the mail system does not confirm inbox delivery. A notice goes to the previously opted-in recipient when alerts are disabled or redirected, subject to those limits. This does not detect every security change, plugin deactivation or direct database edits and is not a replacement for independent monitoring.
The local zeismo_sec_change_alert_budget option holds bounded hashed deduplication records and counters. zeismo_sec_change_alert_status holds the last attempt time and state. These options are preserved on deactivation/deletion with the existing security settings; site owners may remove them through authenticated host access. Your chosen mail provider processes the notification contents.
Two-factor authentication
On a single-site HTTPS installation, open ZEISMO Security > Two-factor as an administrator. Enter your current WordPress password to start. Add the displayed private key to a TOTP authenticator app using manual entry (6 digits, 30 seconds, SHA-1). Confirm a working code within 10 minutes, then save the ten recovery codes in a password manager. Codes are shown only once. Each recovery code works once with your WordPress password.
Enrollment applies only to your account. Your other WordPress sessions are signed out. Subsequent standard WordPress logins require your password plus a fresh authenticator or unused recovery code. Five incorrect codes trigger a five-minute account limit; existing login limits can also apply. Settings changes require your current password and a fresh code. Replacing recovery codes invalidates all earlier codes.
Application-password and XML-RPC access are blocked for enrolled accounts, including previously created application passwords. Review integrations first. Custom login forms, SSO and multisite are not supported by this enrollment flow. This is optional per-account protection, not an enforced sitewide policy. It continues while the firewall is in monitor mode, but stops if the plugin is deactivated.
Setup secrets are encrypted using OpenSSL AES-256-GCM with a key derived from WordPress authentication salts and the user ID. Only keyed hashes of recovery codes are stored. State stays in non-autoloaded local options named zeismo_sec_mfa_USER_ID, with timestamps and attempt counters; no external service receives it. Deactivation and deletion preserve enrollment; deleting the WordPress user removes that user’s state. Changing authentication salts requires re-enrollment. Database backups can restore old codes, so replace recovery codes after a restore.
If the authenticator and all recovery codes are lost, contact the hosting administrator. With authenticated host access and the correct WordPress installation selected, identify the affected user using WP-CLI, then delete only that user’s zeismo_sec_mfa_USER_ID option. This removes their second-factor requirement; verify the account owner’s identity, reset a compromised password, and enroll again immediately. Never accept a public URL or email request alone as authorization for host recovery. There is no public recovery bypass.
Development and source code
All PHP, JavaScript and CSS source is included in this plugin package. The
files in admin/js/ and admin/css/ are the actual readable source used by
WordPress, including admin/js/deactivation.js, admin/css/deactivation.css
and admin/css/toolbar.css. No compilation, minification, npm, Composer or
other build step is required. Edit the bundled source files directly and
test on a development WordPress installation before distributing changes.
This package does not bundle compressed third-party JavaScript libraries.
Request inspection limits
Request-field inspection is capped at eight nested array levels, 256 visited entries across GET and POST, 4,000 bytes per value and 65,536 combined field-name/value bytes. Field names longer than 128 bytes or combined paths longer than 256 bytes are skipped. The request URI has a separate 8,192-byte cap. Sensitive fields are excluded. Inputs beyond these inspection budgets are not examined; reaching a limit does not reject the request. These limits bound plugin inspection work, not PHP request parsing or all denial-of-service traffic.
