Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
85997bca02 | ||
|
|
3aa96c7b3e | ||
|
|
a8108f9b84 | ||
|
|
d89b0d09a9 | ||
|
|
fa1beeb71d | ||
|
|
68cc299d16 | ||
|
|
5657d78e13 | ||
|
|
0fb24b0e7b | ||
|
|
19957d44b0 | ||
|
|
4054510acc | ||
|
|
a0885f319a | ||
|
|
a8cdbef65a | ||
|
|
806094d6a0 | ||
|
|
0faf78287a | ||
|
|
235169e8ac | ||
|
|
67323f0204 | ||
|
|
f3a00c618b | ||
|
|
d39aa6f9bc | ||
|
|
efb0dfc838 | ||
|
|
7fa580d4d6 | ||
|
|
bd3275d252 | ||
|
|
a0f46c0678 | ||
|
|
82dd287445 |
+6
-6
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"version": "7.40.0",
|
||||
"released_at": "2026-09-17T10:42:49+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.40.0/argus-wordpress-defence-7.40.0.zip",
|
||||
"sha256": "9fc415ef804bfd2f584fbaeb69660a0ef963e52773d0c8913cd40d56a78ccd29",
|
||||
"version": "7.63.0",
|
||||
"released_at": "2026-10-08T06:48:51+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.63.0/argus-wordpress-defence-7.63.0.zip",
|
||||
"sha256": "4185f4d090d6edaafe86952c017bc60b7673dd4b39402740872e1b8167a1abbb",
|
||||
"min_php": "7.4",
|
||||
"min_wp": "6.0",
|
||||
"critical": false,
|
||||
"summary": "* Security hardening: this site's IP-based protections (firewall, brute-force login protection,\n REST/API abuse protection, WooCommerce checkout guard, two-factor) now correctly recognise real\n visitor IP addresses when this site runs behind a reverse proxy, load balancer, or CDN, using the\n same trusted-proxy configuration already available under Form Protection. Previously, sites in\n that setup could see every visitor as the same address, weakening these protections.\n* Hardened the replay protection added in 7.39.0 further: it now remembers a short history of\n recently-applied WAD actions instead of only the single most recent one.",
|
||||
"signature": "n97VtOxZFjpDmUbFgbzjnf34nCcGUtGthdhs/oypEyEkidWgY6OiTt4WXUkz3ICEh5RJef9nfYxkyJeNaw1gBQ=="
|
||||
"summary": "* Fixed a real gap in the 7.62.0 Monitor Mode fix: a bot ban or other already-fully-handled event\n could still turn into a second, separate \"suspicious behavior\" finding through Threat\n Correlation, duplicating what the Monitor Mode rollup (or the ban itself) had already covered.\n This no longer happens -- genuinely correlated, multi-signal findings are completely unaffected.",
|
||||
"signature": "PWMBZPER9IETw5Vjdvdly578k5fTmd8BQDCMFdejYQJhd8ShkOmni/hmXVQQ4ap6LAiXhXJd7gfkFincqq08Aw=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user