Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
682a78255d | ||
|
|
2e0c9421f8 | ||
|
|
facfb91f16 | ||
|
|
354ee04d49 | ||
|
|
0b315cc0c7 | ||
|
|
b5d72fecea | ||
|
|
b9d3fba547 | ||
|
|
e37ab80220 | ||
|
|
47b0d553a5 | ||
|
|
7d8aae8b8d | ||
|
|
fc9044d87b | ||
|
|
824e062747 | ||
|
|
9f4627c7c1 | ||
|
|
9647a4c776 | ||
|
|
0f19f0ab30 | ||
|
|
fb6cfa5664 |
+6
-6
@@ -1,11 +1,11 @@
|
|||||||
{
|
{
|
||||||
"version": "8.2.4",
|
"version": "8.6.9",
|
||||||
"released_at": "2026-11-09T16:21:53+00:00",
|
"released_at": "2026-11-20T22:51:30+00:00",
|
||||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v8.2.4/argus-wordpress-defence-8.2.4.zip",
|
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v8.6.9/argus-wordpress-defence-8.6.9.zip",
|
||||||
"sha256": "6b60084ce3acd6142144e16eecb330adab40f59f60e1584c5247abe823a29d60",
|
"sha256": "de235e8e7325436b6e4b4516d1d0b24bc9b674bd038a4d89f20888cd6ca785ba",
|
||||||
"min_php": "7.4",
|
"min_php": "7.4",
|
||||||
"min_wp": "6.0",
|
"min_wp": "6.0",
|
||||||
"critical": false,
|
"critical": false,
|
||||||
"summary": "* Improvement: plugin update now triggers automatic historical security reanalysis \u2014 all existing findings, IPs, bans, and cross-site correlation records are reassessed using the latest detection rules.\n* Fix: trusted proxy auto-detection now covers Cloudflare and RFC 1918 reverse proxies; historical findings caused by misconfigured proxy trust are automatically resolved without banning legitimate infrastructure.\n* Fix: backup schedule hour and minute settings are now correctly preserved after save.",
|
"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": "U/cegjBEK8YNbY/Dwyfzdpbg0D7k0273RJLtnewBOY88X6XtUvdePtXQagRsVKzYW55Do7F3CNz9QHsbzgbnCA=="
|
"signature": "lmAhxd/yPOxu/3JWkZP2Kaz70+MMgwdf2cXBdI2lFb3GdZX+raOM4V+jORDj5D4ZJYW+di9W2CpFHJnSuKHVBw=="
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user