-
v8.6.9 Stable
released this
2026-11-20 22:51:26 +00:00 | 5 commits to main since this release- Fix: the server's own requests (a host cron fetching wp-cron.php with wget/curl, loopback and hairpin calls) are classified internal. The Bot Filter no longer challenges the WP-Cron loopback request, they are never shown on the threat map or counted as attacks, and their events carry ip_class=internal. The firewall still inspects their payloads.
- Hardening: a public visitor cannot claim "internal" with a forged X-Forwarded-For header; forwarded headers from private peers remain untrusted. Loopback addresses (127.0.0.0/8, ::1) are never banned.
= Unreleased = - Fix: a single legitimate request that tripped one firewall signature could earn a 24 h IP ban; all firewall bans now require corroboration.
- Fix: posts and checkout notes containing SQL-like text or a semicolon are no longer matched by the stacked-statement rule; verified editors using the REST API are not blocked or banned for quoting code.
- Fix: Facebook link-shim referrers and a literal "<?php" in the User-Agent/Referer are no longer blocked.
- Fix: a rule exception could be used to hide an attack that repeated the excepted value.
- Fix: forwarded headers from a private address are never trusted automatically; the Cloudflare auto-detection no longer calls a non-existent method.
- New: "1 OR 1=1" style numeric tautologies are detected.
- Clarified: the mode (Monitor by default) and what it does are shown in the admin header and Firewall page.
Downloads