Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
aed69ceb6e | ||
|
|
82b525ca1e | ||
|
|
543bdd58d4 | ||
|
|
1ff0bdbeca | ||
|
|
09ac6a1fda | ||
|
|
2ce45b9c2d | ||
|
|
21ed592b8b | ||
|
|
cc56098488 | ||
|
|
8fa6153099 | ||
|
|
c8f8640e4c | ||
|
|
50336dfd90 | ||
|
|
85997bca02 | ||
|
|
3aa96c7b3e | ||
|
|
a8108f9b84 | ||
|
|
d89b0d09a9 | ||
|
|
fa1beeb71d | ||
|
|
68cc299d16 | ||
|
|
5657d78e13 | ||
|
|
0fb24b0e7b | ||
|
|
19957d44b0 | ||
|
|
4054510acc | ||
|
|
a0885f319a | ||
|
|
a8cdbef65a | ||
|
|
806094d6a0 |
+6
-6
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"version": "7.49.0",
|
||||
"released_at": "2026-09-19T10:22:44+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.49.0/argus-wordpress-defence-7.49.0.zip",
|
||||
"sha256": "c3cb00846010070100534dad41ca4f856df6e76270ab0534c9e13d880068c314",
|
||||
"version": "7.70.3",
|
||||
"released_at": "2026-10-20T08:00:47+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.70.3/argus-wordpress-defence-7.70.3.zip",
|
||||
"sha256": "ecf14ff3b8b526c840ea590388b6f8e058556f88c2196507b14fec2867a34136",
|
||||
"min_php": "7.4",
|
||||
"min_wp": "6.0",
|
||||
"critical": false,
|
||||
"summary": "* A lower-severity WAF detection that keeps being triggered from the same source is now acted on\n automatically -- it is challenged after a sustained run of repeats, and blocked outright if it\n keeps going, instead of staying \"allowed\" indefinitely no matter how many times it recurs.\n* Findings now describe this more specifically: repeated matches from the same source will be\n challenged, then blocked, rather than a generic promise that \"ARGUS will act on it\".",
|
||||
"signature": "Mnk68Wi7lp3s703Qrqe5c7AF7V+V2i79woL/95X/+0qWhGqUkvnkWZIBljU1l5/9ELTG0akkz6tBht1VwlPjAA=="
|
||||
"summary": "* Fixed a case where blocking the web server's own address in ARGUS stopped WordPress's scheduled\n tasks, so the site could no longer report to the portal or receive the instruction to unblock\n it. WordPress's own internal scheduler requests are no longer refused by the firewall.",
|
||||
"signature": "7A9bLx/FEfNMUKGcA5tNEj1laDF8sQU6qaxJKtY/2N/udf50QFtIWrjwD7DGRjn2CWN8ceOPa3pSbvanNkPxCw=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user