Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
aed69ceb6e | ||
|
|
82b525ca1e | ||
|
|
543bdd58d4 | ||
|
|
1ff0bdbeca | ||
|
|
09ac6a1fda | ||
|
|
2ce45b9c2d | ||
|
|
21ed592b8b | ||
|
|
cc56098488 | ||
|
|
8fa6153099 | ||
|
|
c8f8640e4c | ||
|
|
50336dfd90 | ||
|
|
85997bca02 | ||
|
|
3aa96c7b3e | ||
|
|
a8108f9b84 | ||
|
|
d89b0d09a9 | ||
|
|
fa1beeb71d | ||
|
|
68cc299d16 | ||
|
|
5657d78e13 |
+6
-6
@@ -1,11 +1,11 @@
|
|||||||
{
|
{
|
||||||
"version": "7.56.0",
|
"version": "7.70.3",
|
||||||
"released_at": "2026-10-06T12:36:23+00:00",
|
"released_at": "2026-10-20T08:00:47+00:00",
|
||||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.56.0/argus-wordpress-defence-7.56.0.zip",
|
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.70.3/argus-wordpress-defence-7.70.3.zip",
|
||||||
"sha256": "c6a8bb73b91943e69bde39d7ebce5d1ea9670f20e13824f99dd8dd74c9052906",
|
"sha256": "ecf14ff3b8b526c840ea590388b6f8e058556f88c2196507b14fec2867a34136",
|
||||||
"min_php": "7.4",
|
"min_php": "7.4",
|
||||||
"min_wp": "6.0",
|
"min_wp": "6.0",
|
||||||
"critical": false,
|
"critical": false,
|
||||||
"summary": "* Every finding now clearly states whether ARGUS already took action and exactly what it did,\n instead of folding that into the general advice text.\n* A file ARGUS automatically quarantines now shows its own distinct status until you decide\n whether to restore or permanently delete it, instead of looking identical to an untouched,\n unreviewed finding.\n* Correlation-based findings now explain what was found in plain language.\n* Form Protection can now recognise business-inquiry submissions with inconsistent details --\n for example a personal email address on a form that asked for a company name, an email that\n doesn't match the stated company, or a generic, templated-sounding message -- and raises them\n for your review instead of letting them through unnoticed.",
|
"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": "f+9T5Dzv/M0RwXtiEi9K6haHUxgVwwyyGAeEmkPqc7LqDocuSVQMXfuggtjprc3HTpc3TRxuNjUP+uFao9pfDg=="
|
"signature": "7A9bLx/FEfNMUKGcA5tNEj1laDF8sQU6qaxJKtY/2N/udf50QFtIWrjwD7DGRjn2CWN8ceOPa3pSbvanNkPxCw=="
|
||||||
}
|
}
|
||||||
|
|||||||
Reference in New Issue
Block a user