From 0c3ac9e46397f74bc1adb6034f614dc12a0104ff Mon Sep 17 00:00:00 2001 From: Luis Melo Date: Sun, 1 Nov 2026 10:06:45 +0000 Subject: [PATCH] Update signed manifest to 7.74.0 --- manifest.json | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/manifest.json b/manifest.json index dffc569..06fde76 100644 --- a/manifest.json +++ b/manifest.json @@ -1,11 +1,11 @@ { - "version": "7.73.0", - "released_at": "2026-10-31T19:09:01+00:00", - "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.73.0/argus-wordpress-defence-7.73.0.zip", - "sha256": "34877adbeda02cef2046bb7f088c937b6d3d9c16a87596dfe65bca8d08be9300", + "version": "7.74.0", + "released_at": "2026-11-01T10:06:45+00:00", + "package_url": "https://git-cloud.weboria.eu/Weboria/argus-wp-defence/releases/download/v7.74.0/argus-wordpress-defence-7.74.0.zip", + "sha256": "8aeff5ccb8dcb4d8565aa1d5df10b096badc80ca9521949cbf89493c191520f0", "min_php": "7.4", "min_wp": "6.0", - "critical": true, - "summary": "* WordPress core upgrades through ARGUS now use a safe, recoverable process: ARGUS first checks\n that your site is ready for the upgrade, verifies compatibility, takes a validated recovery\n backup, performs the upgrade, and automatically rolls back if a critical problem is detected\n afterwards. The upgrade button now gives a clear explanation if the safe upgrade process is not\n yet enabled on a site, rather than failing silently.\n* The \"Check upgrade readiness\" option now works correctly -- it runs a full compatibility and\n risk analysis and shows a report without making any changes to your site.", - "signature": "Jx2wWfhIZ0UgHekgjBeUH8hBczvbI8smv+nlelScfzgBKUPRTPULYR7q1CZXK6H/nOzncb19GaxnJ66ZbJJ5AQ==" + "critical": false, + "summary": "* Requests for backup files (.bak, .sql, .tar.gz, etc.) and sensitive dotfiles (.git/config,\n .env, .ssh/id_rsa, etc.) are now blocked immediately rather than only monitored. These patterns\n have no legitimate use on a WordPress site and were previously classified as medium-severity,\n which meant they could slip through when spread across many different source addresses.\n Existing open findings for these patterns are automatically re-classified as high-severity.", + "signature": "2HkDgBA5cxqQAtRQhhuM+y/M8oOsxeCWbTBeoPr1qTRfMj+5JPHJ3HUUm2mVbRWUjZZqo8XB+tdvKEhw25nYDQ==" }