Compare commits

...
4 Commits
Author SHA1 Message Date
tech 682a78255d Update signed manifest to 8.6.9 2026-11-20 22:51:31 +00:00
tech 2e0c9421f8 Update signed manifest to 8.6.8 2026-11-20 21:26:22 +00:00
tech facfb91f16 Update signed manifest to 8.6.7 2026-11-18 23:45:56 +00:00
tech 354ee04d49 Update signed manifest to 8.6.6 2026-11-18 21:49:42 +00:00
+6 -6
View File
@@ -1,11 +1,11 @@
{
"version": "8.6.4",
"released_at": "2026-11-17T13:42:52+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v8.6.4/argus-wordpress-defence-8.6.4.zip",
"sha256": "2a3e8f17a4e1d905e0375ff59e16a1e3ca67783c6d054e33f24ef480957f9dce",
"version": "8.6.9",
"released_at": "2026-11-20T22:51:30+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v8.6.9/argus-wordpress-defence-8.6.9.zip",
"sha256": "de235e8e7325436b6e4b4516d1d0b24bc9b674bd038a4d89f20888cd6ca785ba",
"min_php": "7.4",
"min_wp": "6.0",
"critical": false,
"summary": "- Improvement: single-class behavioural correlation findings combining failed logins with user-enumeration probes are now automatically tracked and trigger ban escalation instead of appearing as open findings requiring review.\n- Improvement: existing open attack-recon findings are reconciled to Security Tracking on upgrade.",
"signature": "f9M8VgoDF9Re3QMwHmAC3P0xPst57t6TfHXPuXhHLwiIHBWUFQ8f0aG8I4huh2pm5szCQi+DlTIS0zJISlaMBw=="
"summary": "- 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.\n- 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.\n= Unreleased =\n- Fix: a single legitimate request that tripped one firewall signature could earn a 24 h IP ban; all firewall bans now require corroboration.\n- 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.\n- Fix: Facebook link-shim referrers and a literal \"<?php\" in the User-Agent/Referer are no longer blocked.\n- Fix: a rule exception could be used to hide an attack that repeated the excepted value.\n- Fix: forwarded headers from a private address are never trusted automatically; the Cloudflare auto-detection no longer calls a non-existent method.\n- New: \"1 OR 1=1\" style numeric tautologies are detected.\n- Clarified: the mode (Monitor by default) and what it does are shown in the admin header and Firewall page.",
"signature": "lmAhxd/yPOxu/3JWkZP2Kaz70+MMgwdf2cXBdI2lFb3GdZX+raOM4V+jORDj5D4ZJYW+di9W2CpFHJnSuKHVBw=="
}