Linux 软件免费装
Banner图

Guard Forge – Security, Login Protection, 2FA & Audit Log

开发者 avakodeforge
更新时间 2026年11月9日 14:02
PHP版本: 7.4 及以上
WordPress版本: 7.1
版权: GPLv2 or later
版权网址: 版权信息

标签

security brute-force two-factor-authentication login-protection audit-log

下载

1.6.5 1.9.0 1.9.1 1.6.3 1.5.0 1.3.6 1.6.1 1.3.5 1.8.0 1.4.0 1.6.0 1.6.4 1.7.0 1.8.1

详情介绍:

Guard Forge hardens your WordPress site against common attacks without an account or an API key. It applies hardening rules, watches for brute-force login attempts, protects accounts with two-factor authentication, compares your files with what wordpress.org actually published, and keeps an audit log that shows if anyone edited or deleted a line afterwards. Login protection. Failed logins are counted per IP address; past the threshold the address is locked out and unblocked automatically later. Every logged-in user can switch on two-factor authentication for their own account: a time-based one-time code (TOTP), a login challenge and single-use recovery codes. The QR code for enrolment is drawn on your own server, so the secret never leaves the site. File integrity. Once you switch the monitor on, every core file and every plugin hosted on wordpress.org is compared with the checksums wordpress.org publishes for that exact release. The screen separates files that are official, modified, missing, and not in the official build at all, which is what a backdoor looks like. Premium and custom plugins and all themes have no published checksums, so they are marked "no reference" and never counted as clean. The check asks wordpress.org with a version number and a plugin slug, and never sends your site address or anything about your content. Audit log. Logins, failed attempts, option changes, plugin and theme activity and user and role changes are recorded, and every row carries the hash of the row before it. "Verify chain" walks the table: an edited row no longer matches its own hash, and a deleted row leaves the next one pointing at a hash nothing produces. Hardening score. Twenty-one checks of your own installation add up to a score from 0 to 100. Each row states how many points it is worth and links to the screen that changes it. The score makes no outbound request. Free Pro add-on (separate plugin, not part of this download) Documentation: https://guardforge.app/docs/

安装:

  1. Upload the guardforge folder to /wp-content/plugins/, or install through Plugins → Add New.
  2. Activate GuardForge through the Plugins menu.
  3. Open GuardForge → Settings to review the hardening options.
  4. Visit GuardForge → File integrity to create the initial baseline, and GuardForge → 2FA to protect your own login. Point your other users at GuardForge → 2FA as well — it is the one GuardForge screen every logged-in role can open, and it only ever touches the account of whoever is looking at it.

屏幕截图:

  • The checklist behind the score: each row says what it found, how many points it is worth, and links to the setting that changes it.
  • File integrity against the checksums wordpress.org publishes: here a PHP file that is not part of the official WordPress build, found in wp-includes.
  • Login log: failed attempts per address, and the lockout once the threshold is reached.
  • Hash-chained audit log: user, role, option and plugin changes, and "Verify chain" confirming that every row still points at the one before it.
  • Two-factor authentication for your own account: the enrolment QR code is drawn on your own server and nothing is fetched from anywhere.

升级注意事项:

1.9.1 If you use the add-on, keep GuardForge Pro 1.4.0 or newer installed. The add-on requirement is unchanged. 1.9.0 If you use the add-on, keep GuardForge Pro 1.4.0 or newer installed. The add-on requirement is unchanged. 1.8.1 If you use the add-on, keep GuardForge Pro 1.4.0 or newer installed. The add-on requirement is unchanged. Sites that switch WP-Cron off no longer get the request that wakes it. 1.8.0 If you use the add-on, keep GuardForge Pro 1.4.0 or newer installed. The add-on requirement is unchanged. 1.7.0 Needs GuardForge Pro 1.4.0 or newer if you run the add-on, as before. Moving the site to another address no longer shows the audit log as tampered, and a database update that could not finish now says so. 1.6.5 Needs GuardForge Pro 1.4.0 or newer if you run the add-on, as before. Vulnerability ranges are matched again, the official Two-Factor plugin's second step is left alone, and "Verify chain" no longer cries wolf after the nightly clean-up. 1.6.4 Needs GuardForge Pro 1.4.0 or newer if you run the add-on, as before. Anonymous REST access is no longer blocked by default: only user records stay private, so the WooCommerce cart, forms and webhooks work for visitors again. 1.6.3 Needs GuardForge Pro 1.4.0 or newer if you run the add-on, as before. 1.6.2 Needs GuardForge Pro 1.4.0 or newer if you run the add-on, as before. 1.6.1 Deleting the last Forge plugin or add-on now removes everything Forge stored on the site, on every site of a network. Needs GuardForge Pro 1.4.0 or newer if you run the add-on, as before. 1.6.0 Needs GuardForge Pro 1.4.0 or newer if you run the add-on: the licence code and the License and Alerts screens moved into it, and an older add-on is not started beside this version until you update it. Logs, baselines and settings are untouched. 1.5.0 Settings no longer files checks that have not run yet under “Not working”, reports a switched-on monitor that stays silent, and shows rows that tie in a sort in one fixed order. If you run GuardForge Pro, it must be 1.2.0 or newer. 1.4.0 The Vulnerabilities screen now tells whether GuardForge Pro updates the database each day; the add-on's new daily update and its switch come with GuardForge Pro 1.3.0. If you run GuardForge Pro, it must be 1.2.0 or newer. 1.3.6 The new-administrator alert now fires on every way of granting the role, the REST API and add_role() included, and REST role changes are logged in full. If you run GuardForge Pro, it must be 1.2.0 or newer. 1.3.5 If you run GuardForge Pro, it must be 1.2.0 or newer. 1.3.4 The file-integrity monitor starts off and schedules nothing until you switch it on: its daily comparison asks wordpress.org for the official checksums. If you run GuardForge Pro, it must be 1.2.0 or newer. 1.3.3 Core files are no longer written by this plugin: a modified one is reported, and re-installing WordPress from Dashboard → Updates puts it back. If you run GuardForge Pro, it must be 1.2.0 or newer. 1.3.2 If you run GuardForge Pro, it must be 1.2.0 or newer; an older add-on is switched off whole until you update it. 1.3.1 If you run GuardForge Pro, it must be 1.2.0 or newer; an older add-on is switched off whole until you update it. 1.3.0 If you run GuardForge Pro, it must be 1.2.0 or newer. An older add-on never heard of staging mode and would keep mailing alerts from a clone, so it is switched off whole: alerts, the Cloudflare push, lockdown, the WAF, scanning and required 2FA stop until you update it. Logs and settings are kept. 1.2.0 Adds file integrity checked against the official wordpress.org checksums, a hash-chained audit log you can verify; a hardening score; and staging mode. The 2FA screen now opens to every logged-in role. If you run GuardForge Pro, update it to 1.2.0 too. 1.1.0 Two-factor authentication and full file-integrity monitoring are now free. If you run GuardForge Pro, update it to 1.1.0 at the same time. 1.0.1 Adds the audit log export. Nothing to do on upgrade. 1.0.0 Initial release.

常见问题:

Do I need an account or API key for the free version?

No. Every protection runs on your own server. The one thing that reaches the network needs no account: the file-integrity scan asks wordpress.org for the official checksums of your WordPress version and your wordpress.org plugins, and says nothing about you. See External services above.

How would I know if somebody edited the audit log?

Press "Verify chain" on the audit-log screen. Every row carries the hash of the row before it, so an edited field breaks its own row, and a deleted row leaves the next one pointing at a hash the table cannot produce. The check names the first row that failed. Restoring a database backup over a live log breaks the chain too. On a log larger than fifty thousand rows the check covers the oldest part and says plainly that it was truncated.

What does "not in the official build" mean?

The file-integrity screen sorts files into official, modified, missing, and not in the official build at all. The last group is a file that the release published by wordpress.org does not contain. A backdoor looks like that, and a comparison with yesterday's scan cannot see it, because a shell that was already on disk when the baseline was taken looks exactly like an unchanged file.

Will it update my plugins behind my back?

No. The free plugin does not update anything. The Pro add-on has "Patch by update", which is off until you switch it on. When an advisory names the version that fixes it and WordPress is offering an update that reaches it, the add-on installs that update, one plugin per run, with an allow list and a deny list, and tells you by e-mail and in the audit log.

Does Guard Forge send my data anywhere?

Nothing about your site reaches Avakode from this plugin. Its one outgoing request is the checksum lookup to wordpress.org, and only while the file-integrity monitor is on. The Pro add-on is a separate plugin; its own readme lists what it sends and where.

Will Guard Forge conflict with other security plugins?

Guard Forge does not detect or switch off other security plugins. If two plugins both count failed logins or both write rules to .htaccess, they can overlap, so keep each of those jobs with one plugin. If you notice a conflict, please open a support thread.

How do I get the Pro features?

Pro features ship in a separate Guard Forge Pro add-on. Install this free plugin first, then add Pro from https://avakode.com.

更新日志:

1.9.1 1.9.0 1.8.1 1.8.0 1.7.0 1.6.5 1.6.4 1.6.3