Compare commits
| Author | SHA1 | Date | |
|---|---|---|---|
|
|
50336dfd90 | ||
|
|
85997bca02 | ||
|
|
3aa96c7b3e | ||
|
|
a8108f9b84 | ||
|
|
d89b0d09a9 | ||
|
|
fa1beeb71d | ||
|
|
68cc299d16 | ||
|
|
5657d78e13 | ||
|
|
0fb24b0e7b | ||
|
|
19957d44b0 | ||
|
|
4054510acc | ||
|
|
a0885f319a | ||
|
|
a8cdbef65a |
+6
-6
@@ -1,11 +1,11 @@
|
||||
{
|
||||
"version": "7.51.0",
|
||||
"released_at": "2026-09-19T16:44:43+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.51.0/argus-wordpress-defence-7.51.0.zip",
|
||||
"sha256": "d423a2c0131a1a5b7a6b9761c7db98196466ba2d53aa6d97d0533d8d63bdc91c",
|
||||
"version": "7.64.0",
|
||||
"released_at": "2026-10-08T07:51:53+00:00",
|
||||
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.64.0/argus-wordpress-defence-7.64.0.zip",
|
||||
"sha256": "61cfa4d5f06e158f4c45233393bbb428c17877111cdc44f8858f0ea210889eea",
|
||||
"min_php": "7.4",
|
||||
"min_wp": "6.0",
|
||||
"critical": false,
|
||||
"summary": "* Vulnerability Protection now investigates plugins that are not distributed through\n WordPress.org (private, premium, or vendor-hosted plugins) instead of simply reporting them as\n unchecked. It checks the plugin's own vendor identity, changelog, and available public\n vulnerability sources, and clearly shows what was checked, what was found, and how confident\n the result is.\n* Added a \"Check External Intelligence\" action on the Vulnerabilities page for these plugins, plus\n a dashboard summary of how much of your plugin inventory currently has complete vulnerability\n coverage.\n* Findings for these plugins are now created and cleared automatically as new information becomes\n available, the same way they already are for WordPress.org-distributed plugins.",
|
||||
"signature": "Ed1qDtjAK+OCs7h4HkxCzxmCTTY8t1ONuwa+0UkDekhFawv/nVGDEfsLIVFAwE72s31abrF4itTOyRauA/fnBQ=="
|
||||
"summary": "* Closed a narrower follow-up gap in 7.63.0: an IP that was banned shortly after some failed login\n attempts could still get a duplicate \"suspicious behavior\" finding, because the failed attempts\n that led to the ban were being counted as separate new evidence. A genuinely unresolved attempt\n that never actually got banned is unaffected and still shows up for your review, as before.",
|
||||
"signature": "4OnNOph3V6legWOe/rdi9c3LUANDxKrAvSFg/OKAt3lkRK/zP1Ev7IU2BhqwbBUshmT/0osmzo4k7AluTXdCCA=="
|
||||
}
|
||||
|
||||
Reference in New Issue
Block a user