Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
7d8aae8b8d | ||
|
|
fc9044d87b | ||
|
|
824e062747 | ||
|
|
9f4627c7c1 | ||
|
|
9647a4c776 | ||
|
|
0f19f0ab30 | ||
|
|
fb6cfa5664 | ||
|
|
26dd83e8bc | ||
|
|
c2eae8801b | ||
|
|
a9f7b6ddf9 | ||
|
|
1a959fcdbb | ||
|
|
81d011d56a | ||
|
|
510eab15b3 | ||
|
|
95cb325dd6 | ||
|
|
6bc43378e2 | ||
|
|
99de067d89 | ||
|
|
85bc2b0123 | ||
|
|
830bc5b38a | ||
|
|
407ae0a5f9 | ||
|
|
4d738638a7 | ||
|
|
7c22b85cdf | ||
|
|
027bdc5d06 | ||
|
|
dad8018345 | ||
|
|
91f73b55b0 | ||
|
|
3d2424a027 | ||
|
|
30acc5c9fe | ||
|
|
ada915a068 | ||
|
|
743bf0c7d8 |
+6
-6
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"version": "7.88.0",
|
||||
"released_at": "2026-11-04T10:46:53Z",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.88.0/argus-wordpress-defence-7.88.0.zip",
|
||||
"sha256": "0f7878b935ef9972c40ac3d49dc3717af66e69c59c0a0fd919d642913844281c",
|
||||
"version": "8.5.0",
|
||||
"released_at": "2026-11-15T12:39:35+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v8.5.0/argus-wordpress-defence-8.5.0.zip",
|
||||
"sha256": "d8a21dd3b764d2a0edaa9d6f5b1e9ead551bbddf811fa5b8bde49770287bdc45",
|
||||
"min_php": "7.4",
|
||||
"min_wp": "6.0",
|
||||
"critical": false,
|
||||
"summary": "* New: sensitive option monitor \u2014 blocks unauthorized changes to user registration settings and security keys; flags suspicious privilege escalations. * New: CVE virtual patching \u2014 receives signed, CVE-specific virtual patches from ANIS; blocks requests exploiting known vulnerable plugin versions. * New: behaviour engine \u2014 scores requests on entropy, encoding depth, request rate, user enumeration and failed login signals; auto-escalates to rate-limit or block. * New: WAF deep decoding \u2014 detects attacks hidden behind multiple layers of URL, HTML entity, base64 and hex encoding. * Fix: high-confidence SQL injection (hex-literal variant) was being allowed through instead of blocked. * Fix: settings IP exceptions were still triggering the auto-ban; challenge failures that could not be stored now fail closed; REST user enumeration in Monitor mode now recorded correctly. * New: enforcement_outcome field on findings.",
|
||||
"signature": "5wXstYKwun6EVAYYO5Lx7Xmw8lUXNOMuQE/grZfE3G2qZAMFSdL+3bVGXkS177rieg2jXvOeGeKZfAkdizFzCQ=="
|
||||
"summary": "- Centralized progressive ban escalation policy: all automated ban paths now use a unified TTL ladder (L1 24h, L2 7d, L3 14d, L4 30d max) with a 90-day recurrence window, matching the WAD engine policy. Repeat offenders are banned for progressively longer durations regardless of which detection subsystem triggered the ban.",
|
||||
"signature": "VHnvrDa8mOvrQq+V4IbZqj8uyK8NjIT0To/NeuTAdZUwoHvGVZ7IYG9wtYNzydb3gWv61ln0lz0n/1DmfQYICw=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user