Compare commits

..
5 Commits
Author SHA1 Message Date
tech 85997bca02 Update signed manifest to 7.63.0 2026-10-08 06:48:52 +00:00
tech 3aa96c7b3e Update signed manifest to 7.62.0 2026-10-07 21:41:58 +00:00
tech a8108f9b84 Update signed manifest to 7.61.0 2026-10-07 20:54:26 +00:00
tech d89b0d09a9 Update signed manifest to 7.60.0 2026-10-07 20:29:14 +00:00
tech fa1beeb71d Update signed manifest to 7.59.0 2026-10-07 15:31:33 +00:00
+6 -6
View File
@@ -1,11 +1,11 @@
{
"version": "7.58.0",
"released_at": "2026-10-07T11:13:22+00:00",
"package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.58.0/argus-wordpress-defence-7.58.0.zip",
"sha256": "b140d997084875edafa67a4762f3f7ec5662c17cbf9670a024b092351e950a90",
"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": "* Findings for events ARGUS already handled automatically -- a brute-force IP ban, a bad-bot\n auto-block -- now consistently say so, instead of occasionally still showing \"Nothing\n automatically\" after the action already happened.\n* If an automatic ban ever fails to save, ARGUS now raises its own finding about that failure\n instead of quietly treating the event as resolved.\n* Vulnerability Protection now recognises ARGUS WordPress Defence itself as a trusted, first-party\n component, instead of showing it as an unverified external plugin just because it isn't\n distributed through WordPress.org. A real vulnerability in ARGUS's own code is still detected\n and flagged just the same.",
"signature": "1DvPQAaVW591I8ZNfz4ZVl0xTsJOOzRy1NCcrl3k6vizqbsrG4kvJd3O5lDLD23Q5VsFrUlM5BT/vatxN7soDQ=="
"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=="
}