Linux 软件免费装
Banner图

WAF Manager for Cloudflare

开发者 ja1me4
更新时间 2026年7月24日 13:39
PHP版本: 8.0 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

security firewall cloudflare hardening waf

下载

1.0.22

详情介绍:

This is the WordPress.org edition, and it contains the WAF Rules Builder only. The full version, WP WAF Manager, adds DNS management, zone analytics, zone controls and cache purge, IP access rules, security events, email routing, and multi-account support. It is available free on GitHub, or from wpwafmanager.com for automatic updates and priority support. The full version is fully compatible with this edition and runs on the same site. WAF Manager for Cloudflare lets you deploy a set of battle-tested Cloudflare WAF (Web Application Firewall) rules to any of your Cloudflare zones in one click, right from your WordPress admin — no Cloudflare dashboard or Rules expression language required. WAF Rules Builder Deploy five pre-configured, battle-tested security rules to any Cloudflare zone in one click, based on the open-source wafrules.com ruleset: Each rule is fully customizable with checkboxes — no need to write a single line of Cloudflare expression syntax. Additional builder features: Plugin Settings Requirements External services This plugin connects to the Cloudflare API to read your zones and to create, read, and deploy WAF rules on your behalf. This service is required for the plugin to function — without a Cloudflare account and API credentials, the plugin has nothing to manage. Requests are sent to the Cloudflare API at https://api.cloudflare.com only from your WordPress admin, and only when you take an action that requires it: verifying credentials, testing the connection, listing your zones, listing existing rules, previewing rules, or deploying rules. The data sent consists of the Cloudflare credentials you enter (an API Token, or an account email plus Global API Key), the zone IDs you select, and the WAF rule definitions you build in the plugin. No data about your site's visitors and no personal data about your WordPress users is sent. The plugin does not send data to any other third-party service. Cloudflare is a third-party service operated by Cloudflare, Inc. By using this plugin to connect to Cloudflare, you are subject to their terms and policies: Trademarks This plugin is independent and is not affiliated with, endorsed by, or sponsored by Cloudflare, Inc. Cloudflare is a registered trademark of Cloudflare, Inc., referenced here only to describe what this plugin is compatible with. No endorsement or affiliation is implied.

安装:

  1. Upload the waf-manager-for-cloudflare folder to /wp-content/plugins/ or install via Plugins → Add New → Upload Plugin
  2. Activate via Plugins → Installed Plugins
  3. Navigate to WAF Manager in the admin sidebar
  4. Enter your Cloudflare API Token and click Verify & Save
Creating Your API Token
  1. Visit Cloudflare API Tokens
  2. Click Create Token and start from a Custom Token
  3. Add permissions: Zone → WAF → Edit and Zone → Zone → Read
  4. Set Zone Resources to "All zones" (or specify the zones you want)
  5. Copy the token into the plugin and click Verify & Save

屏幕截图:

  • Rule 2 (Block Aggressive Crawlers & WP Paths) — block scrapers, exploit scanners, and sensitive WordPress paths with checkboxes.
  • Rules 3 and 4 — block or challenge web hosting ASNs and TOR exit nodes, and managed-challenge the large cloud providers.
  • Rule 5 (Challenge VPN Connections & wp-login) — managed challenge for known VPN providers and the WordPress login page.

升级注意事项:

1.0.22 Adds Custom Allow Expressions to Rule 1 for allowing traffic the built-in allowlists don't cover. 1.0.21 Initial WordPress.org release of the WAF Rules Builder.

常见问题:

Does this work on Cloudflare Free plans?

Yes — the WAF Rules Builder works on Free plans. When Cloudflare restricts a rule phase on your plan, the plugin automatically strips it and retries so deployment still succeeds.

Do I need to know the Cloudflare expression language?

No. Every rule is built from simple checkboxes. The plugin generates the correct Cloudflare expression for you, and you can preview it live before deploying.

Is my API token stored securely?

Credentials are encrypted at rest using libsodium (sodium_crypto_secretbox). The encryption key is derived from your site's AUTH_KEY salt, so it is unique to your site and is never stored in the database. Credentials are also saved with autoload disabled, so they are never loaded on front-end page requests. As a best practice, use a scoped API Token with only the permissions listed above rather than your Global API Key.

Can I store credentials outside the database?

Yes. Credentials can be defined in wp-config.php instead of being saved to the database. See the documentation at wpwafmanager.com for the constant format.

What happens when I delete the plugin?

By default, all data is kept (safe for testing or temporary removal). To have all plugin data removed on delete, go to Settings and disable "Keep data on uninstall" before deleting.

更新日志:

1.0.22 1.0.21