Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
682a78255d | ||
|
|
2e0c9421f8 | ||
|
|
facfb91f16 | ||
|
|
354ee04d49 | ||
|
|
0b315cc0c7 | ||
|
|
b5d72fecea | ||
|
|
b9d3fba547 | ||
|
|
e37ab80220 |
+6
-6
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"version": "8.6.0",
|
||||
"released_at": "2026-11-16T12:45:27+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v8.6.0/argus-wordpress-defence-8.6.0.zip",
|
||||
"sha256": "6f63b619f3b77363446f17aebb9a857bf729636199a98a4589d705b28e001e1f",
|
||||
"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": "- Findings that ARGUS already handled automatically (blocked requests, banned IPs) no longer appear in the active Findings list. They stay visible in the Automatically Handled tab with full evidence preserved.\n- New stale-findings sweep: per-IP findings that have been inactive for 14 days are automatically closed, with an honest explanation and all evidence preserved.\n- Brute-force and user-enumeration findings where the attacker IP is already banned are now automatically resolved by the hourly containment sweep.\n- Accept Risk button replaced by False Positive. Historical risk-accepted findings are preserved and display correctly.",
|
||||
"signature": "EAgd3b2TEnOLDdnr1Z3MrgaGl82BFj6Pi0vUovplqS7tRolBTNRVbwSd73WV/s/FUcizyRRQLYqGHETeqIEnAQ=="
|
||||
"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=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user